| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Mapping Cancer Markers Forum
Thread: MCM on Mac OSX Monterey |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I recently upgraded my Mac Mini (Late 2014) to OSX Monterey. Since doing this I appear to have a problem running Mapping Cancer Markers work units. They appear to start, run for around 2minutes, with the elapsed time and progress both increasing, until elapsed time reaches a little over 2 minutes, and then they reset to zero and start again.
I have tried rebooting the machine, resetting the project and am now stuck for how to resolve this. All other work units, such as Open Pandemics are running fine to completion. I really would like to get to the bottom of this problem. Thanks Mick Young |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3315 Status: Offline Project Badges: 
|
Sounds similar to what other MacOS users are reporting after upgrading their MacOS. See the last few posts on this thread:
----------------------------------------https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,43686_offset,15 For now, you should stop running MCM. I've sent a ticket to WCG asking them to look at this issue.  - AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W - AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W - AMD Ryzen 7 7730U 8C/16T 3.0 GHz [Edit 2 times, last edit by Falconet at Nov 1, 2021 11:40:18 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for replying - it's not just me then.
I continue to receive MCM work units, but have been aborting them, but Open Pandemic work units appear to be running normally. Bye for now Mick Young |
||
|
|
Bryn Mawr
Senior Cruncher Joined: Dec 26, 2018 Post Count: 384 Status: Recently Active Project Badges: 
|
Thanks for replying - it's not just me then. I continue to receive MCM work units, but have been aborting them, but Open Pandemic work units appear to be running normally. Bye for now Mick Young You can block them by going to My Contribution > Projects and unticking mcm. |
||
|
|
Nick Batos
Cruncher Joined: Apr 5, 2020 Post Count: 7 Status: Offline Project Badges: 
|
Throw me on the list of people having issues with the Mapping Cancer Mappers work-units. Have a new MacBook Pro which came with macOS Monterey 12.0.1 (wasn't upgraded). Work units run for 1 to 2 minutes and then restart. No other issues on my other computers not running Monterey.
|
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Recently Active Project Badges: 
|
Have a new MacBook Pro which came with macOS Monterey 12.0.1 (wasn't upgraded). Work units run for 1 to 2 minutes and then restart. No other issues on my other computers not running Monterey. Maybe there is a fix for your problem here, Nick. |
||
|
|
Nick Batos
Cruncher Joined: Apr 5, 2020 Post Count: 7 Status: Offline Project Badges:
|
Thanks, but that link referred to a different issue- that being long running jobs (with there answer to increase %CPUtime to 100% which seems kinda crazy unless you want to run into thermal issues). The issue we are seeing is with Macs running macOX 12 (a.k.a. Monterey) is that the Mapping Cancer Markers work units quit and restart after only 1 or 2 minutes. I am not seeing that problem with my other Mac running macOX 11.6.1 (a.k.a. Big Sur). I am also not seeing in on my PCs running Win10
|
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3315 Status: Offline Project Badges:
|
Thanks, but that link referred to a different issue- that being long running jobs (with there answer to increase %CPUtime to 100% which seems kinda crazy unless you want to run into thermal issues). The issue we are seeing is with Macs running macOX 12 (a.k.a. Monterey) is that the Mapping Cancer Markers work units quit and restart after only 1 or 2 minutes. I am not seeing that problem with my other Mac running macOX 11.6.1 (a.k.a. Big Sur). I am also not seeing in on my PCs running Win10 No, the 100% fix is for MCM units that run and restart after 1 or 2 minutes. I run all my devices, including the laptop I'm writing this from at 100% CPU usage on all threads. Maybe you are better off reducing the number of threads if thermal is an issue. Below is an explanation of what both settings mean: Usage limits - Use at most N % of the CPUs: Keeps some CPUs free for other applications. Example: 75% means use 6 cores on an 8-core CPU. - Use at most N % CPU time: Suspend/resume computing every few seconds to reduce CPU temperature and energy usage. Example: 75% means compute for 3 seconds, wait for 1 second, and repeat. - AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W - AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W - AMD Ryzen 7 7730U 8C/16T 3.0 GHz [Edit 1 times, last edit by Falconet at Dec 1, 2021 10:18:38 AM] |
||
|
|
Nick Batos
Cruncher Joined: Apr 5, 2020 Post Count: 7 Status: Offline Project Badges:
|
Thanks! I'll experiment with ramping up the CPU% (while decreasing the # of cores to control thermals) in order to see if that resolves the MCM restart issue. Even if it does, I believe there is still a bug in the MCM work units to trigger this effect even if running at close to 100% CPU load "fixes" the issue. Running this on a new MacBookPro using a M1Pro CPU so thermals shouldn't be a major issue- this CPU really runs cool.
|
||
|
|
Nick Batos
Cruncher Joined: Apr 5, 2020 Post Count: 7 Status: Offline Project Badges:
|
After a number of attempts, I was able to get MCM to occasionally complete using only 88%CPU time. Anything lower and the MCM work units would always restart after 2 to 3 minutes. Using 100%CPU time has allowed me to complete MCMs consecutively. So I was able to use this 'workaround', but obviously this isn't a 'fix'. [10 core M1Pro MacBook Pro, macOX v12.0.1, BOINC v7.16.19],
|
||
|
|
|