Am 23.03.2011 um 11:52 schrieb Mark Dixon: > On Sun, 20 Mar 2011, Dave Love wrote: > >> Reuti <[email protected]> writes: >> >>> We use a fair share functional policy only regarding the slots, hence >>> the default works. Most of the time the slot count is the limiting >>> factor, not the memory (exceptions apply). >> >> How do you do that? Is the documentation wrong in saying you can only >> consider CPU, rather than run time? I'd like to account for jobs which >> tie up resources without burning CPU. > > Am I missing something, or is the execd_params value > SHARETREE_RESERVED_USAGE=true what you need to do this? (see man page for > ge_conf)
Yes, for the SHARETREE, but not the functional policy. Even the parameter ACCT_RESERVED_USAGE doesn't say anything about functional policy, only for the accounting. > It's been an indispensible option for us. I'm not sure why the manual page > has it marked as deprecated, when it's so useful. It's unified with ACCT_RESERVED_USAGE. Most of the time you will set both. -- Reuti > Mark > -- > ----------------------------------------------------------------- > Mark Dixon Email : [email protected] > HPC/Grid Systems Support Tel (int): 35429 > Information Systems Services Tel (ext): +44(0)113 343 5429 > University of Leeds, LS2 9JT, UK > ----------------------------------------------------------------- _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
