Il 25/09/20 00:04, Relu Patrascu ha scritto: > 1. Allow preemption in the same QOS, all else being equal, based on job > priority. You'd risk having jobs continuously preempted by jobs that have been in queue for a bit: once a job starts, it stops accumulating priority -> another job preempts the first, sending it back in queue -> the first job accumulates some more priority and preempts the second -> loop !
> 2. Job size calculation to take into account the number of GPUs > allocated to the job. In a GPU cluster the most valuable currency being > the GPU, not the CPU. Perhaps even parameterize the job size so the user > could choose what to emphasize in calculation: cpu, gpu, memory. IIUC, you can already do that. See TRESBillingWeights option: just set the CPU and RAM to a low value relative to TRES/gpu. -- Diego Zuccato DIFA - Dip. di Fisica e Astronomia Servizi Informatici Alma Mater Studiorum - Università di Bologna V.le Berti-Pichat 6/2 - 40127 Bologna - Italy tel.: +39 051 20 95786
