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

[James Pringle]

Matt --

   You are right -- in general 1 core/node jobs are a very inefficient use
of trillian in general, and qstat is generally accurate in what it
displays. When I have been active on trillian, I have asked people to be
more considerate and efficient in their use of trillian. There are
instructions on how to start multiple jobs on a single node on the home
page.  I can give more pointers.

   The only time it makes sense to have 1 core per node jobs on trillian is
when the job is IO or memory bound. Even in that case, it is usually
inefficient to use trillian. Its cores are much slower than even a recent
laptop, and most of the undergraduate cluster machines on campus are faster
per-core.

   I think it is acceptable to ask running a bunch of 1 PE per node jobs if
they have a quantified need to run on trillian the way they are.

Jamie Pringle


On Tue, Dec 6, 2016 at 12:24 PM, 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
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sr.unh.edu/pipermail/trillian-users/attachments/20161206/ba9c7e0b/attachment.html>