Reuti <[email protected]> writes: > It wasn't limitd to CPU, but also to MEM and IO. Therefore I got the > idea to simply output both (usage and reserved) just all the time.
The code dosen't actually deal with io as far as I can see (calculate_reserved_usage). Here's a suggested man change: --- old-sge/doc/man/man5/sge_conf.5 2011-05-27 11:26:37.000000000 +0100 +++ new-sge/doc/man/man5/sge_conf.5 2011-05-27 11:26:37.000000000 +0100 @@ -1227,11 +1227,20 @@ to the xxQS_NAMExx execution daemon. The following values are recognized: .\" .IP "\fIACCT_RESERVED_USAGE\fP" -.\" fixme: what exactly does reserved mean? Including resource -.\" reservation time? -If this parameter is set to true, the usage of reserved resources is used for the -accounting entries \fBcpu\fP, \fBmem\fP and \fBio\fP instead of the -measured usage. +If this parameter is set to true, the usage of "reserved" (allocated) +resources is reported in the accounting entries \fBcpu\fP, \fBmem\fP, +and \fBmaxvmem\fP instead of the measured usage. This means that the +"wall clock" time (end\-start) is reported instead of CPU time, memory +usage is memory allocation times wall clock time (only computable if +the job requests h_vmem/s_vmem), and maxvmem is the requested +h_vmem/s_vmem; the same scaling by slots is done as without this option. +.br +Note that both the wall clock and CPU times are available normally (see +.M accounting 5 ), +so this option loses information, and "reserved" here has nothing to +do with advance/resource reservation. See also +.I SHARETREE_RESERVED_USAGE +below. .PP .IP "\fIENABLE_WINDOMACC\fP" If this parameter is set to true, Windows Domain accounts (WinDomAcc) @@ -1304,11 +1313,11 @@ signal name, then this signal will be sent as notification signal. .PP .IP "\fISHARETREE_RESERVED_USAGE\fP" -.B Note: -Deprecated, may be removed in future release. -.br -If this parameter is set to true, the usage of reserved resources is taken for the -xxQS_NAMExx share tree consumption instead of measured usage. +If this parameter is set to true, the usage of "reserved" resources is +taken for the xxQS_NAMExx share tree consumption instead of measured +usage. See the description of +.I ACCT_RESERVED_USAGE +above for details. .br .B Note: When running tightly integrated jobs with \fISHARETREE_RESERVED_USAGE\fP set, -- Excuse the typping -- I have a broken wrist _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
