I had to shutdown BOINC to apply some Windows maintenance

The time remaining on my WAH2 WU, after restart, went from 10D 12H to 12D 15H

Is this expected behavior with an orderly shutdown?

I don't trust the time remaining at all. It gets updated due to various reasons and can go back and forth. The best way to check if you've lost work is by tracking the CPU time or fraction done in the properties page. Usually you should only lose the "CPU time since last checkpoint" when BOINC client restarts.

Checkpoints have nothing to do with the guesstimation at remaining time. CPDN does save a checkpoint at regular intervals (hours not minutes). Expected run duration is only recalculated after a trickle-up has occurred, which is at about 5% progress intervals, or a re-start. Until you have completed a number of similar tasks BOINC can't accurately calculate the expected run duration for a task - it uses a very crude estimated for your computer's performance, which is initially quite pessimistic, hence over estimates the expected duration.

it uses a very crude estimated for your computer's performance, which is initially quite pessimistic,

Or very as opposed to quite pessimistic if on a new instance of BOINC you haven't run CPU benchmarks from the tools menu. (running them after you have downloaded tasks doesn't update the estimate, you have to do it first. (I usually forget!)

Thanks for the response



Usually you should only lose the "CPU time since last checkpoint" when BOINC client restarts.

That value is blank in Windows 10 PRO with BOINC Manager 8.0.2 x64



The best way to check if you've lost work is by tracking the CPU time

That value agrees with what is displayed in BOINC manager, and is reset each time BOINC restarts (I had more Windows maintenance last night



I used to be a programmer before I got into the Systems side of things If I had ever written a program that did not checkpoint/savestate upon a normal shutdown, I'd have been told to go back and do it again




Another thing Since I noticed this, I've been monotoring WAH2 a little closer:

There are three processes, and Resource Manager shows NONE of the three getting any CPU time or Disk activity

Another thing Since I noticed this, I've been monotoring WAH2 a little closer:
There are three processes, and Resource Manager shows NONE of the three getting any CPU time or Disk activity

Check in boincmgr the task is actually running and not suspended.

There is a monitor process that communicates between the models and boinc which always runs, though doesn't consume much cpu. Then the two model processes take it in turns to consume 100% cpu.

---

---
CPDN Visiting Scientist

Usually after a reboot if the task is not happy when it is restarted it will abort and fail but I have seen on several occasions after a reboot that the task appears to be running and not abort, no CPU gets used and this can be seen in the Properties of the task. The CPU time reported stays at whatever point it had got up to before it crashed. These are good for Wuprop hours :D

Thanks

I've gone ahead and aborted that WU

---

Usually after a reboot if the task is not happy when it is restarted it will abort and fail but I have seen on several occasions after a reboot that the task appears to be running and not abort, no CPU gets used and this can be seen in the Properties of the task. The CPU time reported stays at whatever point it had got up to before it crashed. These are good for Wuprop hours :D

Yes, that can happen occasionally. It's a very specific bug that I've got on my list of things to fix. All that can be done is to abort the task in that situation.

---

---
CPDN Visiting Scientist