|
NERSC Announcements Message Archive
Select:
[all-announcements]
[users]
[franklin]
[bassi]
[jacquard]
[davinci]
[nug]
[managers]
[ Back ]
Subject: |
possible change to regular_long queue |
Author: |
Francesca Verdier <fverdier_at_lbl.gov> |
Date: |
2002-01-11 13:56:53 |
Dear NUG Queue Committee,
Several users have noticed that a single person can "monopolize" the
regular_long queue for days at a time, and have suggested that since
only three jobs in this class can run at any given time, it would be
fair to impose a limit of one job per user in regular_long.
At the present time a user can have 4 jobs running throughout the
LoadLeveler system, and LoadLaveler does not provide the ability to
limit the number of jobs running in a given class. However, if the NUG
queue committee thinks that we should limit the number of jobs in this
class to one per user, we could implement this restriction ourselves.
One fall-out from such a restriction would be that a regular_long job
batch script could not submit another one -- the user would have to do
the submission for a second regular_long job after the first one ends.
Opinions? We could implement this next week if the queue committeee
thinks it a good idea. Or we could wait for further discussions at our
Jan 17 NUG meeting.
Sincerely,
--
Francesca Verdier email: fverdier@lbl.gov
Group Leader, NERSC User Services phone: (510) 486-7193
Lawrence Berkeley Lab fax: (510) 486-4004
|
|