[Trillian-users] One Node, One Proc Per Node Jobs

[Robert Anderson]

Just wanted to point out that at least one software package is not
being reported correctly.  The NAMD package is being reported as a
running on a single core, which is most likely a batch queuing 
error on my application script.  The code does run one process on the
node but that process is multi-cored and heavily utilizes all of the
nodes CPU resources.

The performance clearly indicates full utilization, so I haven't been
quick to spend time working out the clerical error in the batch
system.   Perhaps there are reasons why fixing this should have a higher
priority.

Just adding a data point, not really trying to defend my laziness.  :)

On Tue, 6 Dec 2016 17:24:00 +0000
"Gorby, Matthew" <Matthew.Gorby at unh.edu> wrote:

> Hello Trillian Users,
> 
> 
> I'm seeing a lot of one node, one proc / node jobs running at the
> moment.  If this is just the way "qstat -a" displays a type of run
> I'm not familiar then please excuse this email.  If those jobs really
> are what they appear to be then may we have one of the admins chime
> in on this issue?  I'd like to know if that is an acceptable use of
> Trillian's resources.  If not, it would be really great to have the
> other 31/32 of those procs available.
> 
> 
> Thanks,
> 
> 
> -Matt
> 
> 
> 



-- 
--------------------------------------------------
Robert E. Anderson -- (603) 862-3489
Associate Director -- UNH Research Computing Center    
http://www.unh.edu/research/rcc
--------------------------------------------------