| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: BOINC slow on vista 32 bit |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
hey guys/girls its been a while since i have run WCG on my pc but i decided to start again. I downloaded the newest BOINC agent and installed. I set it up and its working ok except that the elapsed time goes very slow. For one second to elapse it takes about ten real seconds to go by. So a project that would normally take four hours would really take 40 hours. when i check task manager the load from BOINC on the cpu is not constant, it bounces from zero to 40-48% and I have it set at 25%, why is the load no constant but bouncing and why it is bouncing so high? My specs are vista ultimate 32 bit, core 2 duo, 2gb ram, 250gb HDD. i have let it run over 6 hours and it has only done about one hour of work. any help would be nice. thanks.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
25% isn't a lot. Maybe that's why work is taking a long time to complete.
BOINC is probably readjusting its time estimates after your interval of inactivity. Pausing crunching always messes with the time estimation. The sawtooth CPU profile is normal. It may look like "it bounces from zero to 40-48%", but actually it is going from 0 to 100 very quickly. It will average exactly 25%. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
i understand that it may take longer to complete that's fine but why is the time messed up, it never readjusts the expected time to complete based on what percentage of the cpu I use, if it originally says 4 hours and i have it at 25% it will still say 4 hours if i set it at 100% cpu. that time does not change, all the changes is the speed at which the time advances. the only time a get a true count on the elapsed time is when i set it to 100% cpu.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
BOINC doesn't factor in the throttle directly (maybe it should?) - instead, BOINC computes time estimates based on the recent crunching performance.
|
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Think the Time To Complete column provides the true (estimated) CPU time and not wall-clock. A program like BOINCview attempts to compute an actual wallclock date/time when the job finishes based on real advancing which is anyway difficult as the work unit progress is not truly linear either.
----------------------------------------Sample BOINCview: Done 4:39 CPU hours Time Wallclock: 11:51 To Compute 1:31 CPU hours Predicted Wallclock completion Time: 13:28 Slip 13:28 - 1:31 - 11:51 = 0:06 The machine runs 'presently' at about 94,21% CPU efficiency (cycles allocated to BOINC per BOINCview)
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Jan 9, 2008 10:57:06 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I think that is the main problem, is that it does not recalculate the time based on what percent of the cpu you are using, while folding@home does. that is the one i was using before and when i would change based on how much of the cpu it used, it would recalculate. Also sekerob the time to completion does not chance based on my throttle, that is the problem i am talking about.
|
||
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1684 Status: Offline Project Badges: 
|
Hi civicking,
----------------------------------------what are you crunching for projects ? There is a known and serious performance issue with HCC on multicore hosts. Other projects are running fine with such systems. You can take a look on this thread . Cheers, Yves |
||
|
|
|