HTCondorWiki: Consumption Policies

 
 For example, the following is a cpu-centric resource consumption policy:
 {code}
+# cpus will generally be exhausted first
 CONSUMPTION_CPUS = target.RequestCpus
-CONSUMPTION_MEMORY = 0
-CONSUMPTION_DISK = 0
+CONSUMPTION_MEMORY = quantize(target.RequestMemory, {32})
+CONSUMPTION_DISK = quantize(target.RequestDisk, {128})
 SLOT_WEIGHT = Cpus
 {endcode}
 
 Another slot might be configured with a memory-centric policy:
 {code}
-CONSUMPTION_CPUS = 0
-CONSUMPTION_MEMORY = quantize(target.RequestMemory, {128})
-CONSUMPTION_DISK = 0
-SLOT_WEIGHT = floor(Memory / 128)
+# memory will generally be exhausted first
+CONSUMPTION_CPUS = 1
+CONSUMPTION_MEMORY = quantize(target.RequestMemory, {1024})
+CONSUMPTION_DISK = quantize(target.RequestDisk, {128})
+SLOT_WEIGHT = floor(Memory / 1024)
 {endcode}
 
 Note that the slot weight expression is typically configured to correspond to the "most limiting" resource, and furthermore behaves as a measure of the number of matches remaining on the partitionable slot.
 
-
 {subsubsection: Fast Slot Loading}