|
1)
Message boards :
Number crunching :
Credit reduced
(Message 1484)
Posted 28 Jan 2020 by Dr Who Fan Post: Here is another example of incorrect CPU time -vs- run time: http://yafu.myfirewall.org/yafu/result.php?resultid=5592660 The task was running on a Pentium(R) Dual-Core CPU E5300 @ 2.60GHz Run time 16 hours 55 min 58 sec CPU time 3 hours 6 min 56 sec I abandoned task because it quit accruing CPU time despite the Run Time increasing every second.. I am guessing CPU Time should of actually been close to 1/2 of the Run Time or aprox 8.5 hours. Appears somehow the BOINC wrapper that the actual science tasks runs under lost track of what the science app was doing. |
|
2)
Questions and Answers :
Windows :
Extremely long WU Times
(Message 860)
Posted 1 Jul 2016 by Dr Who Fan Post: SAME PROBLEM with THIS TASK... Went to 100% after several hours and I let it CONTINUE TO RUN for 1 days 12 hours 46 min 20 sec BEFORE ABORTING. NONE OF THE FILES in the slots directory updated its date/time stamp after it reached the 100% mark. Have had this happen once or twice before but I do not think I posted about it. |