-
Notifications
You must be signed in to change notification settings - Fork 279
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
Log instances of delays due to resource limitations and their causes #132
Log instances of delays due to resource limitations and their causes #132
Conversation
…ay message into the log if it isn't a stagger
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ericaltendorf, looks ok to me. Any concerns adding the stagger info to the other statuses?
log.log(msg) | ||
plotting_status = '<just started job>' | ||
jobs = Job.get_running_jobs(cfg.directories.log, cached_jobs=jobs) | ||
else: | ||
# If a plot is delayed for any reason other than stagger, log it | ||
if msg.find("stagger") < 0: | ||
aging_reason = msg |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So ... when we start a new plot job, we'll log the reason it had been delayed? That could be useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It has helped me with tuning my machines by suggesting what resources are lacking. The only downside that I have encountered is that the Log: count message no longer reflects the total number of jobs launched by plotman since delay messages are also counted.
@13thProgression, thanks for joining the ranks of plotman developers. Cheers. |
Fixes #129
Include job age any time that a plot is held off
Insert the last delay message into the log if it isn't a standard stagger delay