[torqueusers] remaining memory on a node
Andrus, Brian Contractor
bdandrus at nps.edu
Fri Aug 12 12:58:05 MDT 2011
Ok. That is what is odd to me.
Pbsnodes is telling me:
status = rectime=1313175218,varattr=,jobs=141859.hamming2.local 141328.hamming2.local,state=free,netload=481480719018,gres=,loadave=0.01,ncpus=16,physmem=24676992kb,availmem=44749640kb,totmem=45159856kb,idletime=617965,nusers=0,nsessions=? 15201,sessions=? 15201,uname=Linux compute-8-33.local 2.6.18-194.17.1.el5 #1 SMP Wed Sep 29 12:50:31 EDT 2010 x86_64,opsys=linux
Wow... I have way more available than is physically in the system!???
>From the node itself:
[bdandrus at compute-8-33 ~]$ cat /proc/meminfo |grep MemTotal
MemTotal: 24676992 kB
So how does mom calculate this??
Naval Postgraduate School
From: torqueusers-bounces at supercluster.org [mailto:torqueusers-bounces at supercluster.org] On Behalf Of Gabe Turner
Sent: Friday, August 12, 2011 10:05 AM
To: Torque Users Mailing List
Subject: Re: [torqueusers] remaining memory on a node
On Fri, Aug 12, 2011 at 05:01:16PM +0000, Andrus, Brian Contractor wrote:
> Is there a simple way to tell what torque/moab sees as unallocated memory on a node?
> I have one node that someone is using, but not quite all the memory and not all the procs.
> When I try testing against it and do a qsub -I -l
> nodes=1:gpus=1,pmem=1k I still get rejection due to memory... Seems odd.
mdiag -n will tell you what Moab thinks the node has for memory, in MB.
pbsnodes <nodename> should tell you what torque thinks; see the 'availmem='
Gabe Turner gabe at msi.umn.edu
HPC Systems Administrator,
University of Minnesota
Supercomputing Institute http://www.msi.umn.edu
torqueusers mailing list
torqueusers at supercluster.org
More information about the torqueusers