-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ad-hoc report: fox heavy GPU usage #522
Comments
The output from the prototype report looks like this (manually reformatted a little b/c good formatting is not currently implemented):
The mark in the left column indicates that the job used at least one full GPU for at least 24h running, note it would also be marked if it used two GPUs at 60%, say, for the same period (120% total). |
I guess that could usefully be showing time as dd:hh:mm:ss. 115675s (the shorter one) is 32.1 hours. 1495751s (the longer one) is 415.5 hours (divided by four cards, so over 100 hours of real time). Plenty other information is available about these jobs, if of interest. |
Fix #522 - ad-hoc report, heavy GPU usage
Experimental / speculative.
This comes out of https://gitlab.sigma2.no/naic/wp2/identify-most-resource-intensive-users/-/issues/1. We will try to create an ad-hoc report that:
Soft dependencies (we can do without them for now):
jobs
#523profile
output for awk is hard to parse #524The text was updated successfully, but these errors were encountered: