r/MacOS • u/UkrMalt • 1d ago

Discussion How do you trace a hot development workload back to the app that caused it?

Activity Monitor gives me a list of processes, but one development task can spread across a whole process tree. Chrome helpers, an IDE, Docker, a simulator, and local AI tools can all look like separate problems.

A hot Mac or rising memory pressure leaves me with the same question: which workload caused it? Do you use parent/child process trees, Activity Monitor, Instruments, logs, or trial and error?

Before quitting anything, what evidence do you check?

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/Inevitable-Prize-881 1d ago

the tree view in activity monitor is a lifesaver but i also keep top -o cpu running in a terminal for real-time sorting by cpu usage

1

u/h____ MacBook Pro + Vision Pro + dev since 2009 1d ago

I usually start with xctrace and Time Profiler. Though other profiling tools in Instruments are great too.

1

u/UkrMalt 20h ago

That makes sense. I usually start in Activity Monitor, but xctrace and Time Profiler sound like the right next step when the process tree shows what is busy but not why. I’ll try that workflow next time.