12dc23f67e
Tests whether CUPTI recycles graphId values after cudaGraphExecDestroy, which would be the only scenario where the graphLaunchCache in TracyCUDA could serve stale entries for a non-matching exec handle. Result (H100, CUDA 12, CUPTI): graphId is a monotonically increasing counter that is never recycled. 22 create/instantiate/launch/destroy cycles produced unique IDs ranging from 2 to 65 (incrementing by 3 per cycle — one unit per node created during graph construction). This confirms that the stale-cache concern raised in code review is not a real risk in practice: two distinct exec handles always have distinct graphIds. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Tracy Profiler
A real time, nanosecond resolution, remote telemetry, hybrid frame and sampling profiler for games and other applications.
Tracy supports profiling CPU (Direct support is provided for C, C++, Lua, Python and Fortran integration. At the same time, third-party bindings to many other languages exist on the internet, such as Rust, Zig, C#, OCaml, Odin, etc.), GPU (All major graphic APIs: OpenGL, Vulkan, Direct3D 11/12, Metal, OpenCL, CUDA.), memory allocations, locks, context switches, automatically attribute screenshots to captured frames, and much more.
- Documentation for usage and build process instructions
- Releases containing the documentation (
tracy.pdf) and compiled Windows x64 binaries (Tracy-<version>.7z) as assets - Changelog
- Interactive demo
An Introduction to Tracy Profiler in C++ - Marcos Slomp - CppCon 2023
Introduction to Tracy Profiler v0.2
New features in Tracy Profiler v0.3
New features in Tracy Profiler v0.4
New features in Tracy Profiler v0.5
New features in Tracy Profiler v0.6
New features in Tracy Profiler v0.7
New features in Tracy Profiler v0.8