You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Task run time displays total time since task was queued. However, if there are jobs queued beforehand, the counter runs while the other tasks are being processed.
What should be the expected behavior?
It would be more useful to show how long the task took to process once it actually started, not since it was submitted/queued.
If time-since-queued is still considered necessary, then we really need both times to be displayed, but at a minimum, processing time should be displayed.
How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? Please include multiple screenshots of the problem! If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)
The image below shows that the time to process plots 3, 4 and 5 is accurately displayed because these were processed simultaneously on separate nodes.
However, plots 6 onwards were processed on a single node, and the time displayed represents the time since each task was queued.
The text was updated successfully, but these errors were encountered:
gjsa73
changed the title
Task processing time is misleading
Task processing time should be shown, not just time-since-queued
Aug 25, 2020
What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)
Chrome 84 on Windows 10
Edge 84 on Windows 10
What is the problem?
Task run time displays total time since task was queued. However, if there are jobs queued beforehand, the counter runs while the other tasks are being processed.
What should be the expected behavior?
It would be more useful to show how long the task took to process once it actually started, not since it was submitted/queued.
If time-since-queued is still considered necessary, then we really need both times to be displayed, but at a minimum, processing time should be displayed.
How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? Please include multiple screenshots of the problem! If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)
The image below shows that the time to process plots 3, 4 and 5 is accurately displayed because these were processed simultaneously on separate nodes.
However, plots 6 onwards were processed on a single node, and the time displayed represents the time since each task was queued.
The text was updated successfully, but these errors were encountered: