| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 8
|
|
| Author |
|
|
Heidi Jansen
Cruncher Joined: Mar 17, 2012 Post Count: 1 Status: Offline Project Badges:
|
Hello,
I apologise if I'm posting this at the wrong place, this is my first post here. I have taken part in the WCG from 2012 until some months ago when my computer forced me to install Windows 10. After this, the WCG units enter and start working as before, but after a few seconds they stop, saying something like (in English) "suspended, CPU is occupied", and never starts again. Today I downloaded the newest version of WCG, but still the same thing happens. My computer is around 5 years old , but still working well. I am nothing above averagely good with computers, but still I would like to contribute, so that is why I ask and hope someone can help me out there. Thank you in advance. Heidi |
||
|
|
enels
Senior Cruncher Joined: Apr 25, 2008 Post Count: 286 Status: Offline Project Badges:
|
You may have wanted or unwanted tasks that are causing BOINC to suspend all tasks. You can check this with task manager. See what the CPU usage is under the performance tab. You can also google the running processes (sort by CPU usage) to see what's going on.
In the BOINC manager under options->computing-> 'Suspend when non-BOINC CPU usage is above' x%. If your other CPU usage from task manager is more than x BOINC will suspend. |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7844 Status: Offline Project Badges:
|
Under Tools on the advanced view of BOINC make sure the computing preferences look like this:
---------------------------------------- Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I found with windows 10 that cortana can be enough to trigger a pause in processing if "while processor usage is less than [25] percent".
May be worth turning off cortana and seeing if this still happens. Also, if newly installed, indexing may be hogging a certain amount of cpu time. |
||
|
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges:
|
Under Tools on the advanced view of BOINC make sure the computing preferences look like this: Cheers & that "While processor usage is less than" 0! That should work for you... ![]() |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
I found with windows 10 that cortana can be enough to trigger a pause in processing if "while processor usage is less than [25] percent". May be worth turning off cortana and seeing if this still happens. Also, if newly installed, indexing may be hogging a certain amount of cpu time. [I think], WCG's recommended setting is 50% (which is where I've had it for a long time). Found that this also enhances the recorded BOINC efficiency... rather than all the processes fighting over the same cycle, heavy user foreground processes executing that bit faster on my work-system. BOINC is yielding, but still tries to steal every spare cycle there is, to me causing latency. Interestingly, MS claims cortana is available for my language, but still seeing "not available in your language region" on my test system. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Going slightly off topic, but does the for the "while processor usage is less than [x] percent" setting, does x refer to total processor use or to each individual processor?
I.e, if I had the setting set to 50% on a dual core system and one core was at 90%, and the other at 0%, would the setting apply to the core at 90% or to the whole system, where overall usage is at 45%? |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Not sure, but it is likely the sum average... the wiki is inconclusive:
"Suspend computing when your computer is busy running other programs." Once effectuated it takes aminimum of 10 seconds before a resume will happen [or more time is being added when longer], which is often enough on my system to have the user burst subside. |
||
|
|
|