| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Cure Muscular Dystrophy - Phase 2 Forum
Thread: CPU time seems to be wrong... |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 11
|
|
| Author |
|
|
Van Fanel
Cruncher Joined: Dec 27, 2006 Post Count: 42 Status: Offline Project Badges: 
|
Hi,
----------------------------------------I switched a Dual Core to this new project yesterday, and today I started noticing something wrong with the CPU times stated in my Results page. For example, take this WU: CMD2_0001-2O72_A.clustersOccur-2O72_A.clustersOccur_521 On the results page it says the CPU time it took to run this WU was 0.51 hours but, in reality, it took 0.75 hours to run, as stated by BOINC Manager (and later confirmed by myself by going through BM's log file). I've monitored other WUs from this project and it seems to be recurrent that the CPU time stated in the results page is lower than the CPU time stated by BOINC Manager. Can anyone else confirm/deny this? Specs: Win XP 32bit, E6300 Dual Core @ 1.86GHz, 1GB RAM, BOINC Manager 6.6.20 [EDIT]: spell check [Edit 1 times, last edit by Van Fanel at May 13, 2009 7:55:50 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Your problem is that BOINC 6.6 reports elapsed time.
We do not support BOINC 6.6. |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
As already mentioned, BOINC Manager v6.6.xx shows run-times, but you can show the cpu-time of a task by selecting it, and click "Properties" (among the buttons down the manager to the left). For both started tasks and finished tasks this will show among other things the cpu-time, example:
----------------------------------------For a not finished task: CPU time at last checkpoint 02:50:51 CPU time 03:49:56 Elapsed time 03:50:56 Estimated time remaining 01:43:31 For a finished task: CPU time 73:55:28 Elapsed time 74:55:10 For finished tasks you can also see the cpu-time (in seconds) in BOINC-directory in job_log_project-url.txt, for WCG this would be in job_log_www.worldcommunitygrid.org.txt The cpu-time is the last on the line, example: 1242253572.916603 ue 18559.987371 ct 4923.173000 fe 45000000000000.000000 nm CMD2_0001-GPDAA.clustersOccur-MYH6.clustersOccur_2501_0 et 4939.348000 This means 4939 seconds, or 1.37 hours cpu-time.  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Or, just don't use BOINC 6.6. Continuing work fetch problems make me quite confident in giving this advice: avoid at all costs!
The minor irritations like that experienced by the thread opener are sideshows compared to the possibility of wasting days with an empty queue, or any of the other things the new scheduler may get wrong. |
||
|
|
Van Fanel
Cruncher Joined: Dec 27, 2006 Post Count: 42 Status: Offline Project Badges:
|
Oh... I failed to notice that now they had Elapsed time instead of CPU time.
Sorry about that.  |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
Or, just don't use BOINC 6.6. Continuing work fetch problems make me quite confident in giving this advice: avoid at all costs! The minor irritations like that experienced by the thread opener are sideshows compared to the possibility of wasting days with an empty queue, or any of the other things the new scheduler may get wrong. Well, maybe I'm just lucky, or maybe it's due to not having a CUDA that seems to give many of the scheduling-problems, but I've had no problems keeping computer busy while running v6.6.20 and v6.6.28... "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I prefer to rely on testing rather than luck.
|
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Or, just don't use BOINC 6.6. Continuing work fetch problems make me quite confident in giving this advice: avoid at all costs! The minor irritations like that experienced by the thread opener are sideshows compared to the possibility of wasting days with an empty queue, or any of the other things the new scheduler may get wrong. Well, maybe I'm just lucky, or maybe it's due to not having a CUDA that seems to give many of the scheduling-problems, but I've had no problems keeping computer busy while running v6.6.20 and v6.6.28... I've asked WCG Techs some time ago to have their future custom package set the GPU functionality to default "off" in the cc_config.xml. It's not and that is confusing the heck out of the client for some (or many, we don't know). The custom "off" is like not going to get applied edit: spelling
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at May 14, 2009 9:47:24 AM] |
||
|
|
Van Fanel
Cruncher Joined: Dec 27, 2006 Post Count: 42 Status: Offline Project Badges:
|
I agree with Sekerob on the work fetch issue.
Actually, I would say that I get more work than what I specify in the buffer (and I don't even have CUDA); this has raised me some problems in terms of meeting the deadlines in the first days after upgrading to 6.6.20. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
I think the 6.6.20 client should work with separate buffer/cache computation for GPU and CPU. Since that release was promoted to recommended by Berkeley "just to get the new scheduler to (GPU) crunchers", and 6.6.21 was released even before that promotion, I continue to question the release policy. I'm testing 6.6.24 now for longer and find serious insufficiency in the network/computing concurrency, issues resurfacing from before the 5.10 days... not fit for general business imho.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
|