Hi,
Right, you want:
"queue_sort_method load" and "load_formula slots".
Per Reuti's link.
You can easily test by submitting some test jobs on an empty cluster and
see that they all get assigned to the same host, leaving other hosts
empty, until the host with the most slots used if filled up.
That's what we use to reduce the contention between many single-slot
jobs and some many-slot jobs.
Regards,
Alex
On 04/16/2013 10:42 AM, Brett Taylor wrote:
Thanks, I already had $pe_slots in my smp definition, so I guess it's already
doing this more or less. It still seems to be a little bit more random than
I'd like, i.e. sometimes it starts them on empty hosts, sometimes it adds them
to hosts that are running things but have enough free slots.
Brett Taylor
Systems Administrator
Center for Systems and Computational Biology
The Wistar Institute
3601 Spruce St.
Room 214
Philadelphia PA 19104
Tel: 215-495-6914
Sending me a large file? Use my secure dropbox:
https://cscb-filetransfer.wistar.upenn.edu/dropbox/[email protected]
-----Original Message-----
From: Reuti [mailto:[email protected]]
Sent: Tuesday, April 16, 2013 12:27 PM
To: Brett Taylor
Cc: [email protected]
Subject: Re: [gridengine users] modify host selection algorithm?
Am 16.04.2013 um 18:11 schrieb Brett Taylor:
Hello,
Is there a way to modify how GE selects which host(s) to run jobs on? For example, if I
have one user submit 10 6-core jobs, can I make sure GE fills up one host before kicking
jobs onto another, instead of "randomly" placing them on separate nodes? I
only have 18 hosts so I'd like to leave as many hosts completely free for other users as
possible.
http://wiki.gridengine.info/wiki/index.php/StephansBlog
Just note, that it will work only for "allocation_rule $pe_slots" this way.
HTH - Reuti
Thanks,
Brett
_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users
