[torquedev] [Bug 86] Implement transparent resource limits

bugzilla-daemon at supercluster.org bugzilla-daemon at supercluster.org
Wed Oct 6 11:55:48 MDT 2010


http://www.clusterresources.com/bugzilla/show_bug.cgi?id=86

--- Comment #4 from Simon Toth <SimonT at mail.muni.cz> 2010-10-06 11:55:48 MDT ---
(In reply to comment #3)
> (In reply to comment #2)
> > Is it compatible with generic resources support?
> > 
> > http://www.clusterresources.com/bugzilla/show_bug.cgi?id=67
> > 
> > I'm asking instead of going through the patch, because the patch is rather
> > long.
> 
> Your patches in #67 are long too, so I had just went through the initial
> explanations in this ticket.  It seems to me that the patches are completely
> orthogonal, because what mine does is it just transfers server or per-queue
> resource limits to the MOM as an additional job attribute and them MOM checks
> if these resource limits aren't exceeded by the job.
> 
> Your patch seem to add the ability to specify the node properties (read,
> resources).  Mine doesn't care about it, it just enforces the limits and kills
> the jobs.
> 
> Feel free to correct me, because I don't understand what your patch does, even
> having read all comments in #67 :(

Well, the server doesn't have any idea what a resource is (right now). You can
specify resources, but the server is pretty much oblivious to their existence
with the exception of resource limits on queues an server (which are enforced).

This adds all the support around resources that makes sense. Like also checking
the nodespec for resource requests, multiplying requests that are per-proces by
the correct value (ppn=2:vmem=2G ->4G), etc...

>From the description I'm guessing that my patch already does what you want but
instead of killing the jobs when they reach the node, mine already rejects the
run request (so the job is never run in the first place).

-- 
Configure bugmail: http://www.clusterresources.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the torquedev mailing list