Am 06.04.2011 um 10:00 schrieb Vic:
Hi Stephen,
I think thats what I was getting at but semantically different.
Yes - it's that semantic difference that's the trouble :-)
The low queue is the borrow queue which can get onto any box but will
give way immediately if there is a hi job
Ah well I have a workaround I can implement for the medium term and we
seem to have
enough large jobs running that the lack of reservations shouldn't
cause too much of a
woreproblem for now.
On 6 April 2011 08:51, Mark Dixon m.c.di...@leeds.ac.uk wrote:
On Tue, 5 Apr 2011, William Hay wrote:
Yep. No problem.
$ qconf -sq group1.q
...
seq_no 0,[@group1.hgrp=10],[@group2.hgrp=20]
...
user_lists group1_users
...
subordinate none,[@group1.hgrp=group2.q=1]
$ qconf -sq group2.q
...
seq_no 0,[@group2.hgrp=10],[@group1.hgrp=20]
...
user_lists group2_users
...
subordinate
Hi all,
Do we have any place yet for SGE related tools contributions? I have a
queue visualization app I wrote (http://www.gracklewolf.com/gridgraph)
that might be useful to others, but I have no idea where to post it.
--Gary
___
users
Greetings,
Is qacct the best way to pull information about a job to see if its:
1) completed
2) timedout
3) killed
4) still running
Thanks,
Bill
___
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users
On Wed, Apr 06, 2011 at 05:31:25PM -0400, William Deegan wrote:
Greetings,
Is qacct the best way to pull information about a job to see if its:
1) completed
Probably.
2) timedout
Elaborate?
3) killed
Probably.
4) still running
No.
More detailed answers:
1) You can check via
Greetings,
Is qacct the best way to pull information about a job to see if its:
1) completed
2) timedout
3) killed
4) still running
Thanks,
Bill
___
users mailing list
users@gridengine.org
https://gridengine.org/mailman/listinfo/users
Jiri forwarded me the URL to his post and I found it fascinating:
Calculating GE Job Priorities
http://olwynion.blogspot.com/2011/04/calculating-ge-job-priorities.html
I've always felt that one of the strengths of GE (unlimited number of
knobs that you can alter) is also one of it's biggest
Hi Chris
Thanks for pointing out this post.
I consider the man page sge_priorities to be the most important
document in grid engine. Its very good to see this post
discussing the topic.
I have been working on a way to visualize sge_priorities because,
well, there are so many knobs
