Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 3
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1366 times and has 2 replies Next Thread
bob@oberhouse.us
Cruncher
Joined: Dec 12, 2017
Post Count: 1
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Unexpected bursts of Kernel_task activity on a Mac mini

I periodically get bursts of Kernel_task activity that brings my computer to a screeching near halt for 10 to 15 seconds. These bursts only occur when I am running the WCG. These bursts run anywhere from every 30 seconds or so to once every few of minutes. In the setup for the application, I have all CPUs throttled to 60% max usage.
I running a late 2012 quad core Mac mini and OSX 10.14.6 and WCG version 7.14.2.
I have another Mac mini running OS 10.13.6 that is not having this problem.

Any ideas on how to stop these bursts?
[Oct 25, 2019 6:18:30 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sgt.Joe
Ace Cruncher
USA
Joined: Jul 4, 2006
Post Count: 7846
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Unexpected bursts of Kernel_task activity on a Mac mini

I would try just running 2 or 3 cores on WCG at 100%. I think what is happening with 60% is you are basically restarting everything periodically and when it starts again after not running for a little bit it is using all low level commands until it gets going again.
Cheers
----------------------------------------
Sgt. Joe
*Minnesota Crunchers*
[Oct 25, 2019 11:39:11 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Unexpected bursts of Kernel_task activity on a Mac mini

Several people seem to think "BOINC is going to take too much of my machine for me to be able to do what I want to do quickly, so I'll throttle it." That's usually a bad idea and causes problems of it's own. I suggest the following:
1) Run everything at 100%. Only when you KNOW that BOINC is getting in the way should you try turning it down. All the BOINC tasks run at background priority, so everything you're doing should win anyway.
2) If find that you DO have a problem (which might include things getting too hot, now the CPU is running at 100%) the first thing to do is restrict the number of threads BOINC can use. While it seems to be sensible to restrict the percentage of CPU it uses, that's generally not a good idea because it's not a simple, smooth process. It's very lumpy and poorly behaved (because it's not being done by the OS, but by a low priority application).

If you have other software that runs at background but your machine somehow depends on it, then you might have an issue with BOINC. Always worth checking what else is running on the sea-bed ...
[Oct 26, 2019 1:01:50 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread