CPUSetter 1.6.12
App that adjusts the number of active cores in your cpu(s)
| Category: | Utilities |
| Price: | Free |
| Popularity: | Low |
| Version String: | 1.6.12 (590) |
| Release Date: | 2024-05-22 |
| Architecture: | Intel & AppleSilicon(ARM) |
| Minimum OS: | macOS 10.13 |
| Vendor Name: | Bryan Christianson |
| Homepage: | www.whatroute.net |
Install App via MacUpdater:
This link works only when MacUpdater is installed on your Mac
Download from the Mac App Store:
Version History 1.6.12 (590)
Changes
With the addition of the Swap graph in the System Stats window, you will need to adjust the spacing of each graph. I apologise for the inconvenience.
• Build with Xcode 15.4.
• Use Sparkle 2.6.2.
• System Stats: Added Preferences/Settings button.
• System Stats: Do not display unused CPU rows.
• System Stats: Show Swap space allocated and used.
• System Stats: Show CPU/GPU/Memory temperatures.
• Processes: Added column to show process arguments.
Description:
CPUSetter adjusts the number of active cores in your cpu(s). It can also enable/disable hyperthreading on supported cpus.
To do this requires administrator access to the machine and a small privileged helper program is installed when you first execute CPUSetter.
A convenient link to the system Activity Monitor is provided so you can observe the impact of changes.
Authentication with your administrator credentials is required to make changes to your system.
The Processes window allows you to change the priority (nice value) of your processes, and to also limit the maximum CPU usage of any of your processes. You cannot adjust processes that do not belong to you.
Be aware that you may severely impact the operation of your system by adjusting these parameters.
Why would you ever want to do this?
Because you can!
Some software is licensed based on the number of active CPUs in the machine. CPUSetter will enable you to be within the terms of your software license.
Power Saving.
Disabling Hyperthreading can help mitigate Spectre/Meltdown expoits.
CPU resources can be allocated according to your particular workflow.
Many Pro Tools users have reported much better throughput by disabling hyperthreading.
Probably other reasons too, just I can't think of them
The Handbrake process has been limited to a maximum of 100% CPU usage (i.e. 1 whole core from the 4 available) and also reniced to a priority of 19. It is constrained as can be seen by it requesting more CPU resource than it is allowed to use.
