sge_accounting (5) - Linux Man Pages
sge_accounting: Grid Engine accounting file format
accounting - Grid Engine accounting file format
DESCRIPTIONAn accounting record is written to the Grid Engine accounting file for each job having finished. The accounting file is processed by to derive accounting statistics.
FORMATEach job is represented by a line in the accounting file. Empty lines and lines which contain one character or less are ignored. Accounting record entries are separated by colon (':') signs. The entries denote in their order of appearance:
qnameName of the cluster queue in which the job has run.
hostnameName of the execution host.
groupThe effective group id of the job owner when executing the job.
ownerOwner of the Grid Engine job.
job_numberJob identifier - job number.
accountAn account string as specified by the or -A option.
- Priority value assigned to the job corresponding to the priority parameter in the queue configuration (see
submission_timeSubmission time (GMT unix time stamp).
start_timeStart time (GMT unix time stamp).
end_timeEnd time (GMT unix time stamp).
failedIndicates the problem which occurred in case a job could not be started on the execution host (e.g. because the owner of the job did not have a valid account on that machine). If Grid Engine tries to start a job multiple times, this may lead to multiple entries in the accounting file corresponding to the same job ID.
exit_statusExit status of the job script (or Grid Engine specific status in case of certain error conditions). The exit status is determined by following the normal shell conventions. If the command terminates normally the value of the command is its exit status. However, in the case that the command exits abnormally, a value of 0200 (octal), 128 (decimal) is added to the value of the command to make up the exit status.
- For example: If a job dies through signal 9 (SIGKILL) then the exit status becomes 128 + 9 = 137.
ru_wallclockDifference between end_time and start_time (see above).
The remainder of the accounting entries follows the contents of the standard UNIX rusage structure as described in Depending on the operating system where the job was executed some of the fields may be 0. The following entries are provided:
- ru_utime ru_stime ru_maxrss ru_ixrss ru_ismrss ru_idrss ru_isrss ru_minflt ru_majflt ru_nswap ru_inblock ru_oublock ru_msgsnd ru_msgrcv ru_nsignals ru_nvcsw ru_nivcsw
projectThe project which was assigned to the job.
departmentThe department which was assigned to the job.
granted_peThe parallel environment which was selected for that job.
slotsThe number of slots which were dispatched to the job by the scheduler.
task_numberArray job task index number.
cpuThe cpu time usage in seconds.
memThe integral memory usage in Gbytes cpu seconds.
ioThe amount of data transferred in input/output operations.
categoryA string specifying the job category.
iowThe io wait time in seconds.
pe_taskidIf this identifier is set the task was part of a parallel job and was passed to Grid Engine via the qrsh -inherit interface.
maxvmemThe maximum vmem size in bytes.
aridAdvance reservation identifier. If the job used resources of an advance reservation then this field contains a positive integer identifier otherwise the value is "0" .
ar_submission_timeIf the job used resources of an advance reservation then this field contains the submission time (GMT unix time stamp) of the advance reservation, otherwise the value is "0" .
COPYRIGHTSee for a full statement of rights and permissions.