Ronny T. Lampert wrote: > Please note that ANY! newer jobs that might trigger preemption will NO > LONGER WORK with this setup, since maui is only using its scheduling > algorithms on those 50 jobs. > Same with higher prio jobs or similar that will/must/should be executed > ASAP. > You essentially turn your setup into a "50 jobs a at time" batching > system. > > So, depending on your needs you should increase the max_queueable. > > > Before maui I managed to run a heavily patched pbs_sched (early torque > releases) with I think around 20k+ jobs queued. > > After that I abandoned that setup because I needed preemption (sorry, no > docs left from that time). > I had maui running with 10k+ jobs (and changed the #define so it would > consider 8K instead of 4K jobs for real scheduling), but it's not nice > and it'll eat memory like it's sugar (500MB+ RSS). > And I still think scheduling over 8K jobs is far too less for such a > system. > > > Because ATM I no longer have this setup in operation I did stop working > privately on maui to remedy those shortcommings.
Excellent comments Ronny, thank you. -- Jeremy Mann [EMAIL PROTECTED] University of Texas Health Science Center Bioinformatics Core Facility http://www.bioinformatics.uthscsa.edu Phone: (210) 567-2672 _______________________________________________ mauiusers mailing list [email protected] http://www.supercluster.org/mailman/listinfo/mauiusers
