It seems there are no checkpoints. BoincTasks didn't count checkpoints and after restarting of Boinc the WUs are starting from the beginning.
/ 
Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7496
Credit: 44,029,375
RAC: 36,320
It seems there are no checkpoints. BoincTasks didn't count checkpoints and after restarting of Boinc the WUs are starting from the beginning.
Checkpoints are every 10min. Check the entry in the ini file or the entry in stderr.txt
/ Reply
Quote
But no value shows up in the "CPU time at last checkpoint" in the properties window of a task. And when BOINC is shut down and restart, the elapsed time starts from 0 again. Is it the problem of BOINC Manager? I am running version 7.4.27 (x64).
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7496
Credit: 44,029,375
RAC: 36,320
But no value shows up in the "CPU time at last checkpoint" in the properties window of a task. And when BOINC is shut down and restart, the elapsed time starts from 0 again. Is it the problem of BOINC Manager? I am running version 7.4.27 (x64).
Hmm, I have tested it before and it has restarted from the last endpoint. I will try to run a test again with a last number.
Edit:
The checkpointing is still working but the client resets the time back to 0. I will see what time is reported at the end. The only way to save the credits is to go to fixed credits in this situation.
Here is a snippet of the stderr.txt
116*784^199865-1, bit: 540000 / 1921651 [28.10%]. Time per bit: 1.114 ms.
116*784^199865-1, bit: 550000 / 1921651 [28.62%]. Time per bit: 1.095 ms.
116*784^199865-1, bit: 560000 / 1921651 [29.14%]. Time per bit: 1.099 ms.
116*784^199865-1, bit: 570000 / 1921651 [29.66%]. Time per bit: 1.095 ms.
116*784^199865-1, bit: 580000 / 1921651 [30.18%]. Time per bit: 1.093 ms.
116*784^199865-1, bit: 590000 / 1921651 [30.70%]. Time per bit: 1.088 ms.
08:28:15 (5884): wrapper (7.5.26012): starting
08:28:15 (5884): wrapper: running llr.exe ( -d -oPgenOutputFile=primes.txt -oPgenInputFile=input.prp -oDiskWriteTime=10 -oStopOnPrimedK=1 -oOutputIterations=10000 -oResultsFileIterations=99999999)
Base factorized as : 2^4*7^2
Base prime factor(s) taken : 7
Resuming N+1 prime test of 116*784^199865-1 at bit 539521 [28.07%]
Using AVX FFT length 224K, Pass1=896, Pass2=256, a = 3
116*784^199865-1, bit: 540000 / 1921651 [28.10%]. Time per bit: 23.224 ms.
116*784^199865-1, bit: 550000 / 1921651 [28.62%]. Time per bit: 1.098 ms.
116*784^199865-1, bit: 560000 / 1921651 [29.14%]. Time per bit: 1.092 ms.
116*784^199865-1, bit: 570000 / 1921651 [29.66%]. Time per bit: 1.096 ms.
116*784^199865-1, bit: 580000 / 1921651 [30.18%]. Time per bit: 1.093 ms.
116*784^199865-1, bit: 590000 / 1921651 [30.70%]. Time per bit: 1.093 ms.
116*784^199865-1, bit: 600000 / 1921651 [31.22%]. Time per bit: 1.092 ms.
116*784^199865-1, bit: 610000 / 1921651 [31.74%]. Time per bit: 1.091 ms.
Result:
116*784^199865-1 is not prime. RES64: C6E0C43C432904DA. OLD64: 54A24CB4C97B0E8D Time : 2253.202 sec.
08:55:49 (5884): llr.exe exited; CPU time 1534.566237
/ Reply
Quote
yes the app does write checkpoints and picks them up when restarted.
and no - the silly wrapper of course does not pick up the time elapsed already.
SNAFU.
/ Reply
Quote