Hello,
I have some Sierpinski / Riesel Base - long3 v0.27 running.
After 20 hours and about 90% the WUs were paused by the boinc manager to run other project tasks. Back to SRbase the Sierpinski / Riesel Base - long3 v0.27 started from 0%. Are the first 20 hours now lost? I have set to keep the work in memory during pause.
Will this WUs running endless until deadline, because every pause will do a restart?
/ 
Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7257
Credit: 42,729,227
RAC: 1
Hello,
I have some Sierpinski / Riesel Base - long3 v0.27 running.
After 20 hours and about 90% the WUs were paused by the boinc manager to run other project tasks. Back to SRbase the Sierpinski / Riesel Base - long3 v0.27 started from 0%. Are the first 20 hours now lost? I have set to keep the work in memory during pause.
Will this WUs running endless until deadline, because every pause will do a restart?
Can you pls check the stderr.txt from one WU and post the lines here? We can calculate the estimated runtime and check the last checkpoint.
/ Reply
Quote
23:15:04 (1567192): wrapper (7.2.26012): starting
23:15:04 (1567192): wrapper: running llr2_64 ( -oGerbicz=1 -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999)
19:02:36 (1822175): wrapper (7.2.26012): starting
19:02:36 (1822175): wrapper: running llr2_64 ( -oGerbicz=1 -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999)
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7257
Credit: 42,729,227
RAC: 1
23:15:04 (1567192): wrapper (7.2.26012): starting
23:15:04 (1567192): wrapper: running llr2_64 ( -oGerbicz=1 -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999)
19:02:36 (1822175): wrapper (7.2.26012): starting
19:02:36 (1822175): wrapper: running llr2_64 ( -oGerbicz=1 -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999)
ah, linux, a new wrapper with more output is in work, 2 entries could be a restart, no infos about checkpoints but dont worry about the 0 time, if a checkpoint was reached it will restart from the last point.
/ Reply
Quote
Thanks!
Is the percentage value in the Boinc manager linear?
I had 20hours=90%, which means 1%~0,22hours.
After now additional 3,5hours (=+35%) I would have originally 105%.
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7257
Credit: 42,729,227
RAC: 1
Thanks!
Is the percentage value in the Boinc manager linear?
I had 20hours=90%, which means 1%~0,22hours.
After now additional 3,5hours (=+35%) I would have originally 105%.
If the client contacting the server the percentage is based from the last results overall, I dont know if you can have more than 100% but in this case it could be restarted from the last savepoint.
/ Reply
Quote
The WUs were running since additional 13 hours now. I dont see any hint of a checkpoint.
Are 40-50 hours normal run time for Sierpinski / Riesel Base - long3 v0.27 on a Ryzen 5950X?
/ Reply
Quote
rebirtherVolunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 2 Jan 13
Posts: 7257
Credit: 42,729,227
RAC: 1
The WUs were running since additional 13 hours now. I dont see any hint of a checkpoint.
Are 40-50 hours normal run time for Sierpinski / Riesel Base - long3 v0.27 on a Ryzen 5950X?
No, should be done in around 16h, maybe less, tested on my 3950x single core with only 2 lines on start, AVX2 should be faster, cache issues, some Gerbicz check failed errors or throttling?
I recommend to run the long with app_config like -t6 or -t8 on ryzen, less heat and faster run.
/ Reply
Quote
On Linux *buntu you could try this:
top
to get llr2 process id
Output:
1907473 boinc 39 19 95932 63068 3604 R 96,0 0,8 32:32.78 llr2_64
e.g. your $PID is 1907473.Then
sudo strace -e trace=write -s 128 -p 1907473
to attach your process and trace writes.
Output:
strace: Process 1907473 attached
a few moments later...write(1, "74*1010^195186-1, bit: 145465 / 195186 [74.52%], 134178 checked", 63) = 63
write(1, ". Time per bit: ", 17) = 17
write(1, "13.266 ms.", 10) = 10
write(1, "\r", 1) = 1
And don't forget
Ctrl+C
to detach.
Output:
^Cstrace: Process 1907473 detached
/ Reply
Quote