Il 25/05/2016 01:15, Ryan Novosielski ha scritto: > The reason I most often want to do something like this is that as a sysadmin, > I’ll notice someone who has requested 1 core but is really using 16, for > example. In many cases, I will not have noticed this for quite awhile, and > the job is running on a node by itself (because it is common for people to > request full nodes). I’d like to adjust the allocation for this job to > prevent other jobs from using the cores that are in use. What I did is the other way around: I've used cpuset to "pin" the job to the allocated CPUs. This way the real state and the scheduler's view are the same even with misbehaving jobs (we've had 3rd party executables that automatically used every CPU in the system). *Way* less need to watch closely the cluster :)
-- Diego Zuccato Servizi Informatici Dip. di Fisica e Astronomia (DIFA) - Università di Bologna V.le Berti-Pichat 6/2 - 40127 Bologna - Italy tel.: +39 051 20 95786 mail: diego.zucc...@unibo.it 5x1000 AI GIOVANI RICERCATORI DELL'UNIVERSITÀ DI BOLOGNA Codice Fiscale: 80007010376
