4 ms·
> Load your current Mac up with the apps you normally use together when working, and watch their use in Activity Monitor’s CPU History window. If its P cores ar
by elAhmo 3y ago
> Load your current Mac up with the apps you normally use together when working, and watch their use in Activity Monitor’s CPU History window. If its P cores are fully occupied much of the time, and that workload often spills over to the E cores, then you should aim for an M3 with more P cores
Author mentions we can use Activity monitor to see where are apps running, in P or E cores, but I am unable to see this. Can anyone share how to check this? Running the latest Sonoma update
- pram 3y agoWindow -> CPU History ⌘3
- elAhmo 3y agoThanks, I was looking at the CPU tab and thought something changed in the CPU Load in the bottom.
- evulhotdog 3y agoYou can double click the cpu graph at the bottom of the process list, which is probably quicker than going through the menu bar.
- chatmasta 3y agoSemi-related fun fact: if you open Activity Monitor with sudo from the command line, you get a lot more metrics and knobs to turn.
- krackers 3y agoHow exactly do you do this? When I try sudo <binary path> it immediately sigkills with a "launch constraint violation". And I tried on 10.8 from back before SIP was a thing, and didn't see any difference in terms of the per-process metrics I could sort by.
- inferiorhuman 3y agoLaunch an app bundle with open(1).
- chatmasta 3y agoThis works for me (macOS 13.5): sudo '/System/Applications/Utilities/Activity Monitor.app/Contents/MacOS/Activity Monitor' But it's certainly possible that I'm forgetting about some protection I had to disable to make it work. According to my notes, the reason I saved this command is because it let me see the list of open files and ports. But I'm actually not seeing those when running it now...
- krackers 3y agoYou can get open files and ports even without sudo for non-root processes by just hitting cmd+i. Maybe running with sudo might allow you to sample or get files for processes owned by root (presumably the info is same as what you'd get with lsof though). (And by ports it seems to mean network ports. If you want mach ports, you can use lsmp).
- inferiorhuman 3y agoThat doesn't work on MacOS 14. It fails with a code signing violation. You need to use open(1) for app bundles.
- krackers 3y agoIf you want to see this per-process instead of in aggregate, xcode instruments cpu counters can show you which core a thread is running on.
- deleted 3y ago[deleted]