Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Extended Sierpinski Problem :
Odd sieve behavior, still validated?
| Author |
Message |
|---|
|
|
|
So, I started off my new year this morning updating my GPU drivers and rebooting this machine: http://www.primegrid.com/show_host_detail.php?hostid=372374. When BOINC came back on line, I noticed that I had ESP sieve WUs running beyond 100% completion, one even went as high as 3500% done, but the run times when they finished (progress resetting to 100%) were actually lower than the typical runtimes of normal units (18-20 minutes), but were still being validated against other computers.
3 of the 4 tasks:
http://www.primegrid.com/workunit.php?wuid=416564960
http://www.primegrid.com/workunit.php?wuid=416565354
http://www.primegrid.com/workunit.php?wuid=416868085 - (still pending at this moment, but this was the 3500% WU)
Is this a quirk? An error? A loophole for disreputable types? All the WUs that were later downloaded are running normally to 100% and completing in the expected time.
____________
Eating more cheese on Thursdays. | |
|
|
|
So, I started off my new year this morning updating my GPU drivers and rebooting this machine: http://www.primegrid.com/show_host_detail.php?hostid=372374. When BOINC came back on line, I noticed that I had ESP sieve WUs running beyond 100% completion, one even went as high as 3500% done, but the run times when they finished (progress resetting to 100%) were actually lower than the typical runtimes of normal units (18-20 minutes), but were still being validated against other computers.
3 of the 4 tasks:
http://www.primegrid.com/workunit.php?wuid=416564960
http://www.primegrid.com/workunit.php?wuid=416565354
http://www.primegrid.com/workunit.php?wuid=416868085 - (still pending at this moment, but this was the 3500% WU)
Is this a quirk? An error? A loophole for disreputable types? All the WUs that were later downloaded are running normally to 100% and completing in the expected time.
Unless I'm missing something, only one of those elapsed times looks unusually low (the middle of those three). The other two are around 1100 seconds, which is in line with all your other tasks.
Sometimes BOINC has trouble with recording time correctly. I suspect it has to do with starting and stopping the task, but that's just a guess on my part. In any event, there's probably nothing wrong with the task itself.
As for the 3500% completion, I don't know. But if the task completed and validated, it was probably just a BOINC quirk and nothing to worry about if it only happens once.
____________
My lucky number is 75898524288+1
(I am NOT an administrator anymore, so please don't PM me with questions. I can't help.) | |
|
Message boards :
Extended Sierpinski Problem :
Odd sieve behavior, still validated? |
