After years of repeatedly struggling with vtune installs in cloud environments just to get a few specific hw metrics only to fall back on manually building some perf stat events from Perfmon, I finally just built the functionality I always wanted. It automatically generates the set of hardware counters required for your requested metrics, formats it, and then parses the output to evaluate the metric formulas on the raw events

Despite flamegraphs being very intuitive I still have people ask me, what do I look at? Instead of explaining my usual cmd+f's over an over I made a tool which can annotate flamegraphs.

Another downside of flamegraphs is you cannot easily aggregate across multiple stacks without multiple cmd+f's.

The backend is a git repo anyone can add their cmd+f's and optimizations they look for. https://github.com/perfsea/optimizations/blob/main/data/flam...

better than transparent?

I'm conflicted about this one. march native definitely. Have you seen substantial gains from omitting frame pointers?

lol never knew about this thanks. Has this actually slowed down someone's code?

also less logging. Seen this pop up way too many times

Log, but keep it in a buffer. On an unhandled exception or crash, emit all logs relating to the exception (such as per request/rpc).

Agreed. If you're on AWS, CloudWatch can get really expensive really quickly.

I like the idea. Small nit: the scrolling is a little unintuitive.

Thank you for your feedback! I shall take a closer look and perform a UI overhaul.

I wonder how effectively it can utilize all of its execution units for common workloads. Frontend boundedness is often a big issue especially with jit