CPU time resets after WU restarts.

Message boards : Number crunching : CPU time resets after WU restarts.

Author	Message
Conan Send message Joined: 7 Dec 14 Posts: 38 Credit: 15,713,038 RAC: 11,690	Message 322 - Posted: 28 Dec 2014, 11:28:35 UTC Last modified: 28 Dec 2014, 11:31:32 UTC
	I noticed this output on a work unit 11:08:37 (21223): wrapper (7.2.26012): starting 11:08:37 (21223): wrapper: running llr64 ( -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999) 12:41:38 (21223): llr64 exited; CPU time 5523.472304 12:41:38 (21223): called boinc_finish 14:26:34 (21765): wrapper (7.2.26012): starting 14:26:34 (21765): wrapper: running llr64 ( -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999) 14:26:35 (21765): llr64 exited; CPU time 0.002999 14:26:35 (21765): called boinc_finish Note how the CPU time went from 5,523.472304 seconds to 0.002999 seconds which then records a 0.00 second CPU time when uploaded. This task 916010 899422 424 27 Dec 2014, 17:41:17 UTC 28 Dec 2014, 4:28:05 UTC Completed and validated 5,583.16 0.00 150.00 Sierpinski / Riesel Base - long v0.01 Conan
	ID: 322 · Rating: 0 · rate: / Reply Quote

rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 8050 Credit: 68,474,963 RAC: 0	Message 324 - Posted: 28 Dec 2014, 12:04:25 UTC - in response to Message 322.
	I noticed this output on a work unit 11:08:37 (21223): wrapper (7.2.26012): starting 11:08:37 (21223): wrapper: running llr64 ( -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999) 12:41:38 (21223): llr64 exited; CPU time 5523.472304 12:41:38 (21223): called boinc_finish 14:26:34 (21765): wrapper (7.2.26012): starting 14:26:34 (21765): wrapper: running llr64 ( -d -oPgenInputFile=input.prp -oPgenOutputFile=primes.txt -oDiskWriteTime=10 -oOutputIterations=50000 -oResultsFileIterations=99999999) 14:26:35 (21765): llr64 exited; CPU time 0.002999 14:26:35 (21765): called boinc_finish Note how the CPU time went from 5,523.472304 seconds to 0.002999 seconds which then records a 0.00 second CPU time when uploaded. This task 916010 899422 424 27 Dec 2014, 17:41:17 UTC 28 Dec 2014, 4:28:05 UTC Completed and validated 5,583.16 0.00 150.00 Sierpinski / Riesel Base - long v0.01 Conan Its a wrapper issue, it doesnt save the runtime but the last checkpoint thats why Iam using fixed credits.
	ID: 324 · Rating: 0 · rate: / Reply Quote

Carlos Pinho [Black Sheep] Send message Joined: 27 Dec 14 Posts: 10 Credit: 499,710 RAC: 0	Message 326 - Posted: 28 Dec 2014, 12:40:08 UTC
	Where's the residue of this number?
	ID: 326 · Rating: 0 · rate: / Reply Quote

rebirther Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 2 Jan 13 Posts: 8050 Credit: 68,474,963 RAC: 0	Message 327 - Posted: 28 Dec 2014, 12:44:57 UTC - in response to Message 326. Last modified: 28 Dec 2014, 12:45:25 UTC
	Where's the residue of this number? Linux has no output but its in the result file. I have contacted Jean (dev of llr) to take a look into it.
	ID: 327 · Rating: 0 · rate: / Reply Quote

Post to thread

Message boards : Number crunching : CPU time resets after WU restarts.