СmDock "long" and "short" tasks applications

Message boards : News : СmDock "long" and "short" tasks applications
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4

AuthorMessage
Brian Nixon

Send message
Joined: 10 Feb 21
Posts: 21
Credit: 4,809,645
RAC: 2,400
Message 2012 - Posted: 26 Feb 2023, 9:35:38 UTC - in response to Message 2011.  

Yeah – just seen that: #20. Thanks!
ID: 2012 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Brian Nixon

Send message
Joined: 10 Feb 21
Posts: 21
Credit: 4,809,645
RAC: 2,400
Message 2015 - Posted: 26 Feb 2023, 15:49:34 UTC - in response to Message 2008.  
Last modified: 26 Feb 2023, 16:47:06 UTC

Thinking about it some more: this is probably only part of the story. It explains why BOINC gets “CPU time since checkpoint” wrong, but not why tasks’ elapsed CPU time resets to zero after being stopped and restarted.
---
Edit: Having tested it just now, I can confirm Mad_Max’s findings: forcibly updating the last-write time of docking_out.chk does cause BOINC to update all the related internal stats – including “Elapsed CPU time at last checkpoint”, which is saved for use after a restart to initialise the CPU time. And looking at the BOINC client code, it is clear that this only gets done when the last-checkpoint time reported by the wrapper changes.
ID: 2015 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Previous · 1 · 2 · 3 · 4

Message boards : News : СmDock "long" and "short" tasks applications

©2024 SiDock@home Team