Am 02.06.2011 um 19:01 schrieb Dave Love: > Reuti <[email protected]> writes: > >> There is none. It's like outlined here: >> >> http://blogs.oracle.com/sgrell/entry/grid_engine_scheduler_hacks_least > > Apologies for the confusion. However, that doesn't deaql with > multi-level sorting on seqno and load. In an inhomogeneous cluster, > you typically want to sort by seqno (node type) first. At > least in that case, the second-level packing using slots for the load > doesn't work for us in the serial case either. There's a > one-liner fix for the parallel case in the Univa repo, but I don't know > what's the problem in the serial case.
To use "seqno" and as a second sort criteria "load" should work automatically. What behavior do you notice instead: - only sorted by "slots"? - only sorted by "seqno" ignoring the load? (Is it the same with the load_formula being np_load_avg or only with the consumable complex?) -- Reuti _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
