magic-trace VS tracy

I really like magic-trace [0].

https://github.com/janestreet/magic-trace

Not that the exact tracing relies on Intel PT - support for AMD was added recently but uses perf so suffers from the same sampling/skew issues, but is still very useful.

Would love to see this integrate with magic trace [1]. I'll need to look at the code for the flamegraph plugin, because handling nanosecond timestamps in flamegraphs seems to break most tools due to float precision.

(1) https://github.com/janestreet/magic-trace

As for inner workings, have you looked into magic trace? I want to play around with it but last I checked, it doesn't work on macs.

I really hope he can work with cloud vendors and Intel to make Processor Trace a more popular and easier to use capability.

It's unfortunate how https://github.com/janestreet/magic-trace and PMUs in general can't be used by lots of people using cloud VMs.

Magic-trace – High-resolution traces of what a process is doing\ (133 comments)

i don't really think there is _anything_ that comes even close to tracy https://github.com/wolfpld/tracy.

on top of this, given google's penchant for dumping projects aka abandonware, this would be an easy pass.

The RemedyBG debugger (https://remedybg.handmade.network/) and the Tracy profiler (https://github.com/wolfpld/tracy) both use Dear ImGui and so far I've only read high praise from people who used those tools compared to the 'established' alternatives.

For tools like this, programmers are also just "normal users", and from the developer side, I'm sure they evaluated various alternatives with all their pros and cons before settling for Dear ImGui.

Not the person you asked, but generally you might want to look at "frame-based" profilers. These are typically used in video games, but the concept is general, and can apply to other applications. The "frame" could also be something like a request or transaction being processed. I like Tracy[1], myself.

Another latency metric that you'll see, often w/respect to web apps and microservices is "P99" and similar. This is the amount of time in which 99% of requests get their response. For a higher percentile, you get a better idea of worst-case performance.

[1] https://github.com/wolfpld/tracy

I've not actually used Superluminal, but I use Tracy for similar reasons. It's free though (and, importantly, open source).

For profiling, you can check tracy.

You could try Tracy

There is no such thing as overengineering in fun projects, so I've also adopted Tracy as profiling solution. Works quite nice and gonna save me plenty of times in the future debugging performance spikes on badly optimized math heavy operations.

I know about tools such as tracing, jaeger or tracy. While having a complete tracing could be a potential solution, these tools don't work with no_std.