News for hackers. Stuff that matters.
Re:Google/orbit – C/C++ Performance Profiler by signa11 on Monday February 12, 2024 @12:25AM (#39341690)
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.

Re:Google/orbit – C/C++ Performance Profiler by Veserv on Monday February 12, 2024 @01:43AM (#39342171)
Does tracy support automatic function entry/exit (FEE) traces (i.e. all functions are automatically instrumented with a start/end)? The documentation seems to indicate traces are all manual which is pretty inconvenient. There are very few cases where you even need manual instrumentation if you have FEE data from my experience.
Re:Google/orbit – C/C++ Performance Profiler by cmovq on Monday February 12, 2024 @01:08AM (#39341961)
What surprised me about Tracy was just how easy it was to include in a C++ project. Just compile and link a single .cpp file (TracyClient.cpp)
Re:Google/orbit – C/C++ Performance Profiler by Jamie9912 on Monday February 12, 2024 @03:15AM (#39342667)
Orbit doesn't require you to change any code at all, according to their readme
Re:Google/orbit – C/C++ Performance Profiler by zokier on Monday February 12, 2024 @04:50AM (#39343167)
What about vtune? I was under the impression that it is pretty much the state of art in profiling
Re:Google/orbit – C/C++ Performance Profiler by maccard on Monday February 12, 2024 @09:00AM (#39344810)
ETW Traces are the gold standard for most uses IMO - https://randomascii.wordpress.com/2015/09/24/etw-central/.

For architecture specific profiling, Vtune is still pretty good though.

Re:Google/orbit – C/C++ Performance Profiler by pjmlp on Monday February 12, 2024 @09:16AM (#39344985)
JFR is also quite good, for those on the JVM world.
Re:Google/orbit – C/C++ Performance Profiler by sahlab on Monday February 12, 2024 @07:49AM (#39344213)
Tracy is amazing. Having just integrated it into a major project, it's leaps and bounds above what we were using previously.