| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: GO Fight Against Malaria
Thread: Unit not 'crunching' |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 4
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
So I have 4 cores - 3 cores working perfectly on other Boinc projects
25% of CPU 'free' - and gfam unit is not processing - just incrementing time to completion (upto 39hr 52 mins and increasing) Reading posts on this forum gfam seems to be unrelaible - I'll support other projects instead |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
"seems" the operative word. If you run BOINC with the CPU time % active (usual default 60% at WCG for absolute erring on the save side), the VINA based units at times get stuck. Same for DSFL and SN2S.
----------------------------------------Inviting to reading more posts offers workaround, with substantially better overall response of your system at that... more results and lower fan noise... that is, if you really need to slow down BOINC due to excess CPU temps for which the BOINC throttle was designed, the only reason it exists at all. Most normal running desktops don't need this 60% limitation. My Linux quad runs 56C atm (hottest core, and coolest at 52C) at 100% CPU time setting and CPU fan fixed speed of 2419-2428RPM. --//-- edit: Insert project in topic. [Edit 1 times, last edit by Former Member at Mar 2, 2012 2:54:09 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
k
Well today cpu is at 100% (ish) same as its managed for the last month - aprt from the 'stuck' gfam job yesterday |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi,
100%(ish) is really not 100%. The setting pointed at is "Use at most 100% of CPU Time", of course to be read as "Use at most 100% of [spare] CPU time". This is for the WCG kit, Standard profile, set at 60%. How it works at for instance 95% is, that the client will run 19 seconds and pause 1 second [to cool down]. You'll appreciate the silliness of this, but that's how it works at the moment. If temperature is not an issue, recommend to set this value to 100% or simply through the Activity menu: Run always. Let us know if we need to work on the temperature as there are 2 good alternate solutions to slowing BOINC... the GFAM/DSFL forum discussed ThreadmasterGUI and TThrottle. For both there are items in the Start Here FAQ index to read up on. --//-- |
||
|
|
|