[torquedev] Cpuset behavior in TORQUE 3.0

Garrick Staples garrick at usc.edu
Fri Jul 2 13:28:01 MDT 2010

On Fri, Jul 02, 2010 at 03:24:53PM -0400, Troy Baer alleged:
> One other thing I've noticed with cpusets in TORQUE 2.4.5 on the
> small-ish UV system to which I currently have access is that the cleanup
> of a job's cpuset after the job ends is *extremely* slow for jobs using
> large numbers of cores (>100) on a node.  It looks like pbs_mom creates
> a cpuset for every core allocated to the job underneath the job's
> cpuset, and removing those takes significant time (several minutes in
> some cases) because they're removed sequentially, one at a time.  Worse,

I think that was taken out in trunk some time ago.

Garrick Staples, GNU/Linux HPCC SysAdmin
University of Southern California

Life is Good!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.supercluster.org/pipermail/torquedev/attachments/20100702/87a84fc2/attachment.bin 

More information about the torquedev mailing list