Saagar Jha (@saagar@saagarjha.com)

Saagar Jha

04/07/2025 (replying to Saagar Jha)

Anyway I have actual work to do so I’ll play with this later. It’s very rough but also very cool and I expect it to be invaluable for any serious performance or debugging work. I hope to see it continue to improve :)

Saagar Jha

04/07/2025 (replying to Saagar Jha)

Also, fair warning: the entire process to generate the screenshots above created about 4 TB of disk traffic. Hopefully you have AppleCare

4 replies →

4 replies

Jevin Sweval

04/07/2025 (replying to Saagar Jha)

@saagar fffffffuuuuuuuuuuuu well that’s disappointing. Guess we need to figure out how to plug one of the 4U units in.

https://www.exostivlabs.com/exostiv-blade/

Kacper Harasim

04/07/2025 (replying to Jevin Sweval)

@jevinskie @saagar Developers can control how much data gets recorded using the recording options ("Limit to:"). We recommend starting with smaller traces, which should not consume as much RAM and load faster as well. We're devoted to continuing to optimize this experience and offering reasonable performance for larger traces over time.

Saagar Jha

04/08/2025 (replying to Kacper Harasim)

@KacperHarasim @jevinskie Curious what this number corresponds to

Jevin Sweval

04/07/2025 (replying to Saagar Jha)

@saagar is it tracev3 format? I wonder if some other compressor could be hooked in…
Any idea how the trace system avoids self-tracing/minimizes perturbation?

Pierre H.

04/07/2025 (replying to Jevin Sweval)

@jevinskie @saagar that’s not how tracing works. The CPU traces everything and then the trace is post processed. You know which asid is current and prune it