| 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 for CMD2 being reduced to 6 hours |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
raybon
Cruncher Joined: Dec 2, 2005 Post Count: 29 Status: Offline Project Badges: 
|
This is the first time I've seen this for a project. On the actual client I'm seeing elapsed run times from 6-10 hours, but when they show up on the site it seems like most of them are being set to 6.00-6.03 hours.
----------------------------------------Anyone else seeing this?  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Elapsed time of 10 hours translates to 6 hours CPU time [which is what is reported to the website, and the standard cutoff for HCMD2]. Your client is likely default set to 60% CPU time, and to ''run based on preferences". You can increase that if it's a desktop to 100%. For laptops it is wise to closely monitor CPU temperature as cooling for these is often insufficient to run at 100%... the reason why WCG sets it to 60%.
--//-- |
||
|
|
raybon
Cruncher Joined: Dec 2, 2005 Post Count: 29 Status: Offline Project Badges:
|
Mine is set to
----------------------------------------On multiprocessor systems, use at most 100% of the processors Use at most 100% CPU time Run based on preferences Could be I just noticed this weirdness because of the huge estimated time remaining the first couple days of CMD2 units had. |
||
|
|
|