If you find the approach cumbersome, you can also use the nohup command directly. A more elegant approach would of course be to let it go to the background and execute it without affecting the continued use of our terminal. However, after executing the command, the program will occupy the current terminal because of its internal dead-loop logic. To make it easier to use, we can put the executable under / usr/local/bin, so that it can be executed directly in any directory later. This will ensure that it is not killed and does not slow down your Mac, so it can be called " not to die, not to live". The first parameter is the pid of the process, the second parameter is the maximum CPU usage percentage, suppose a security software process id is 7218, you only allow it to eat up to 50% of entire CPU. Once you get the pid of an app, enter the below command to limit the CPU usage of the app. Now, find the pid of running apps with ps command: I thought this old OS X style software was no longer working on current versions of macOS, but to my surprise, it is still working on latest macOS Monterey like a charm if you want to limit CPU usage on Mac, probably due to the good compatibility with stable kernels (Basically, there is no OS kernel that changes system calls regularly).Īfter downloading cputhrottle.gz and unpacking it, open Terminal app and grant permission to run this app. The developer provides the source code and compiled binary executable on its official page. This tiny tool has no GUI and is a lightweight utility based on command line.
Perhaps you are wondering, what kind of people would have this need? You have this need when some companies force their employees to install " xx security software" and from time to time it scans files in the background and eats CPU like crazy, and you are not allowed to close and uninstall it. This allows users or developers to have the opportunity to make system calls to fulfill a requirement – to limit the CPU usage of a process or app. Broadly speaking, GUI layer is a close source, which is the essence of macOS the core system (darwin-xnu) is open source. But what do we do when we really need to limit Mac CPU usage for a specific app?Īs we know, Apple’s macOS is a half-open and half-closed operating system. It was discovered a long time ago that Activity Monitor on Mac is really just a pure monitoring service and cannot be set manually by the user to prioritize processes like Task Manager on Windows OS.
0 kommentar(er)
