| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Mapping Cancer Markers Forum
Thread: MCM 7.44 huge processing time |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 11
|
|
| Author |
|
|
erwinmaes
Cruncher Joined: Nov 28, 2014 Post Count: 9 Status: Offline Project Badges: 
|
Compared to the 7.43 versions (average 4-6 hours processing time), my fastest computer in the network now gets 7.44 version of the MCM and this takes more than 24 hours to process, and it gets stuck at 100% and keeps processing...
On my other computers (Linux) 7.43 gives me no problems.... Is 7.44 for Mac? And why now suddenly does it take like forever to process.. The first batches of MCM on this fast Mac processed in 2,5hours....  |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7846 Status: Offline Project Badges: 
|
The first thing I would try is a reboot of the system. Try that and let us know.
----------------------------------------Cheers
Sgt. Joe
----------------------------------------*Minnesota Crunchers* [Edit 1 times, last edit by Sgt.Joe at May 23, 2020 4:49:14 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Declaring versions of science apps is not exactly a strong point of WCG, searching the forums a 7.44 is found for apple-darwin during the January 08 test in an error log, 7.43 goes back to Oct.2018 and is for Linux. The January 08 2020 beta seems to be more about testing a new work type then about testing a new version, so guess 7.44 actually is too from Oct.2018. The January 22, 2020 Beta was only for Android to test a new platform addition. Version per error logs somewhere in the range of 7.53.
----------------------------------------Just rolling some dice and see what numbers come up. [Edit 1 times, last edit by Former Member at May 23, 2020 4:42:47 PM] |
||
|
|
erwinmaes
Cruncher Joined: Nov 28, 2014 Post Count: 9 Status: Offline Project Badges:
|
I rebooted twice, the 7.44 keeps processing extremely slow.
The Mac where the 7.44 is running is a quad core 3,6 GHz Intel Core i7 32 GB 2400 MHz DDR4 The 7.43 runs on a dual core pentium that only runs at 1,66 Ghz and that one is 7 times faster... So there is an issue with the 7.44 MCM for Mac... |
|||
|
||||
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7846 Status: Offline Project Badges:
|
I rebooted twice, the 7.44 keeps processing extremely slow. The Mac where the 7.44 is running is a quad core 3,6 GHz Intel Core i7 32 GB 2400 MHz DDR4 The 7.43 runs on a dual core pentium that only runs at 1,66 Ghz and that one is 7 times faster... So there is an issue with the 7.44 MCM for Mac... One more suggestion. Suspend everything except for one MCM. See if it continues to run slow or if it speeds up. Also check to see what else might be using cpu cycles. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Mike.Gibson
Ace Cruncher England Joined: Aug 23, 2007 Post Count: 12594 Status: Offline Project Badges: 
|
Try checking Task Manager to see CPU %.
Mike |
||
|
|
erwinmaes
Cruncher Joined: Nov 28, 2014 Post Count: 9 Status: Offline Project Badges:
|
I solved the problem by setting max CPUS to 75%, it was on 100% since a few days, and that triggered the problem.
Now it's on 75% CPU's and 50% processor time and it runs fine! On Linux this problem does not exist (I use 100% of the CPU's at 50% processor time) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
75% of threads and 50% of time is using 37.5% of capacity with the latency to add for on and off and on and off ever second. Try 50% of threads at 100% of time, which should bypass the hyperthreading completely. You'll see them flying (no and it's not the popular piglets that get mention on these forums).
----------------------------------------[Edit 1 times, last edit by Former Member at May 25, 2020 7:26:52 AM] |
||
|
|
erwinmaes
Cruncher Joined: Nov 28, 2014 Post Count: 9 Status: Offline Project Badges:
|
Lavaflow : If I do that, my processor fans start turning at max immediately and don't stop...
75% of the CPU's and 60% time is the maximum without stressing my machine :-) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It certainly pays to attack the dustbowl inside your computer, every 3 months at least. Did it last week, particularly the heatsink, after stopping the computer, and after that the temps dropped 10C, fans no longer in medium high rev state, just a gentle hiss.
As I noted, 50% of CPU time will cause BOINC to alternate every second, run 1, pause 1, which is the cooldown phase. If a MCM1 job at 100% would run 3 hours CPU time, which is about the normal for my device, on wallclock it will need 6 hours or so. With hyperthreading on the task would too run 6 hours 'CPU time' at 100%, but with HT on, that could easily turn 12 wallclock hours at 50%, so now we understand. Think you would do much better by reducing the CPU cycles. No idea how to do this under OSX, but under Windows it would be going to the power app Power & Sleep > Additional power settings > Change Plan Settings > Change Advanced Power Settings and under the Processor Power Management change the Maximum Power State to a lower than 100% value. High summer I set it to 70%. The CPU runs slower, still 100% load, but in task manager you'd see 70% utilization, lots less heat, and still maximum 'CPU time' crunched, and that's what makes the clock tick for most badge hunters. |
||
|
|
|