On Friday, February 11, 2011 17:29:39 Alexander Willner wrote: > Dear maui users, > > I've a problem that was discussed on this list quite often (e.g. [1]) but > still I couldn't find a solution (even though I've tested [2]). The > problem can be described as follows: > > 1. We have different Torque queues for users for different clusters. > 2. When a user submits e.g. about 10.000 jobs into one queue (e.g. called > 'long'), jobs in other queues (e.g. 'short') are not started by maui. 3. > This happens because only 4096/3.810 (see [3]) jobs are considered by > maui. > > Since we don't want to reduce the maximum number of jobs that can be > submitted to a single Torque queue, I would like to configure maui to > consider e.g. only the top 500 jobs *of each* queue instead of handle all > jobs of all queue equally. > > I would be very happy to get your opinions on this issue. > > Best regards, Alex > > [1] http://www.mail-archive.com/[email protected]/msg00322.html > [2] http://www.supercluster.org/pipermail/mauiusers/2007-April/002705.html > [3] http://www.supercluster.org/pipermail/mauiusers/2004-August/001303.html > > -- > net.cs.bonn.edu/willner
We have upped the job limit significantly, we currently set the limit to 32000, but you need to recompile maui for this. A solution might be to use routing - execution queue pairs, where the execution queue has an upper limit of jobs it can hold. I have not tested this and do not know if you still will run up against the hard upper limit of jobs maui will hold in its internal buffers. It might be worth a try as it could be that maui only consider jobs from execution queues. r. _______________________________________________ mauiusers mailing list [email protected] http://www.supercluster.org/mailman/listinfo/mauiusers
