#client #profiler #bindings #crates #level #project #libraries

tracy-client

High level bindings to the client libraries for the Tracy profiler

7 unstable releases (3 breaking)

0.10.0 Nov 18, 2020
0.9.0 Oct 11, 2020
0.8.0 Aug 26, 2020
0.7.4 Aug 4, 2020
0.7.3 Jun 24, 2020

#36 in Profiling

Download history 18/week @ 2020-08-06 18/week @ 2020-08-13 23/week @ 2020-08-20 22/week @ 2020-08-27 26/week @ 2020-09-03 30/week @ 2020-09-10 10/week @ 2020-09-17 14/week @ 2020-09-24 10/week @ 2020-10-01 41/week @ 2020-10-08 34/week @ 2020-10-15 44/week @ 2020-10-22 55/week @ 2020-10-29 196/week @ 2020-11-05 249/week @ 2020-11-12 190/week @ 2020-11-19

241 downloads per month
Used in 2 crates

MIT/Apache

11MB
207K SLoC

C++ 187K SLoC // 0.0% comments C 17K SLoC // 0.1% comments Visual Studio Project 1.5K SLoC Rust 441 SLoC // 0.0% comments HLSL 368 SLoC // 0.0% comments Objective-C 209 SLoC // 0.1% comments Visual Studio Solution 186 SLoC Batch 3 SLoC // 0.4% comments Shell 2 SLoC

Tracy profiler clients in Rust

This project contains Rust crates for producing Tracy profiler traces. Tracy features nanosecond precision, ability to profile remotely and a full-featured graphical interface for finding hot spots in profiled programs.

While Tracy's support for Rust is not first-class, it is still a very potent tool. If you have an application instrumented with the tracing crate, Tracy can be used with your program in minutes via the tracing-tracy crate. It can work well as both a profiling and, to a lesser extent, an observability tool.

Important note

Simply depending on crates in this repository is sufficient for tracy to be enabled at program startup, even if none of the APIs provided by this crate are invoked. Tracy will broadcast discovery packets to the local network and expose the data it collects in the background to that same network. Traces collected by Tracy may include source and assembly code as well.

As thus, you may want make sure to only enable the tracing-tracy, tracy-client and tracy-client-sys crates conditionally, via the enable feature flag provided by the crates.

Version support table

This project, unlike Tracy itself, follows semantic versioning. We will publish a breaking version bump whenever there is a breaking protocol change, even if the Tracy project itself does not. An older version of Tracy being unable to communicate with the client of a more recent version is an example of such a breaking change.

The following table lists the version correspondence between the libraries.

Tracy tracy-client-sys tracy-client tracing-tracy
0.7.1 0.9.0 0.8.0 0.2.0
0.7.3 0.10.0 0.9.0 0.3.0
0.7.4 0.11.0 0.10.0 0.4.0

Dependencies