Recommendation on how to optimize App Tamer
I have the M1 Max 64GB which only has 2 efficiency core, I am running macOS Sequoia 15.7.7 I have a few high CPU usage apps: Microsoft Edge (I use it instead of Safari, for personal and work), Outlook, Teams and Claude desktops (I am not using Claude Code,…
I have the M1 Max 64GB which only has 2 efficiency core, I am running macOS Sequoia 15.7.7 I have a few high CPU usage apps: Microsoft Edge (I use it instead of Safari, for personal and work), Outlook, Teams and Claude desktops (I am not using Claude Code, only chat). At seats these are the top apps in Activity Monitor. Then, some medium CPU usage apps: Things 3, plus the standard Apple apps: Mail, Messages, Finder, Calendar, etc. Then, I have a few Menu Bar background apps: Moom, Clamshell, OpenUsage, BetterDisplay, Shortery, Paste and App Tamer, they are low usage (in theory) but are running 24x7. I have setup all the high CPU usage apps to run on the Efficiency Cores and Slow them down if they go above 10%, but I think with only 2 Efficiency Cores is not a very efficient approach, thoughts? Then, for the medium usage apps only to Slow them down if the go above 10%, what should I do with the Menu Bar apps? Any strategic advice on how to efficiently configure App Tamer (I am using the latest beta 3.0b12 (13111)) for overall efficient use of the MacBook Pro 16, thank you
已收录讨论
I'd say don't bother too much with taming all apps—you should trust that most apps are well designed, and macOS handles them properly. App Tamer should only be used to restrict the ones that really behave badly. Otherwise, you're both wasting your time and your MacBook's power by making things run slower.
Thanks
With only two efficiency cores on that machine, the biggest mistake is taming everything: the E cores saturate and the whole machine feels laggier while the P cores sit idle. I would tame only what genuinely lives in the background (Teams and Outlook are good candidates) and leave the browser alone, since it is foreground most of the day. One check worth doing before taming anything: open Activity Monitor and watch the hot app over a few hours, including its thread count. Steady moderate load is what App Tamer is built for. A slow climb in CPU or threads over hours is usually a leak inside the app, and no amount of core pinning fixes that; restarting the app resets it, and reporting the numbers to the developer is the actual fix. I spent yesterday chasing exactly that pattern in a Mac app and the giveaway was thread count creeping up hour after hour while the app looked idle.
I haven't actually customized much with it, but it still doubles my battery life just by accepting suggestions when they pop up to tame apps. If an app has a tendency to freeze, then I might allow more before taming, or temporarily disable apptamer.
i would not try to force all the busy apps onto efficiency cores. with only 2 of them, you can end up making the machine feel worse while not saving much. start by watching which app is actually burning CPU while idle. browsers, teams/outlook, and ai chat apps are usually the ones worth taming. for those, use slow down when idle/backgrounded, but give them a higher threshold than 10% if you notice lag when switching back. for menu bar apps, i would mostly leave them alone unless one shows up in Activity Monitor over time. tiny background utilities often cost less than the overhead/friction of managing them.
switch 2 Dia browser!