[Index] [Quick Jump] Enable to actually call the Tracy functions and produce data. Otherwise the wrappers will be no-ops. Enable if your libtracyclient has this enabled. Enable if your libtracyclient has this enabled. Manually manage profiler lifetime. Enable if your libtracyclient has this enabled. Don't generate and keep events if there's no connection. Enable if your libtracyclient has this enabled. Crash when a zone is starting on an unbound thread. Skip the bound-thread check for zones. This may crash the profile server with "zone ended twice" error. Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info Package maintainers For package maintainers and hackage trustees Candidates Haskell bindings for Tracy frame profiler. You can install the prebuilt package from your distribution if it has one: Or you can download and build one yourself and point your project to it: You can use the provided Makefile that will do the thing: This way you can customize configuration. Make sure you update package flags to match. Either way, you have to ensure that tracy-capture/tracy-profiler is built with the same version. Otherwise it will connect and immediately refuse to record anything. The flags must match whatever the library has been built with. By default all the instrumentation wrappers do nothing. That means you don't have to ifdef your code to remove the wrappers when they're not needed. You have to set the enable flag in your project for the data to be collected. Use the functions from System.Tracy and System.Tracy.Zone to collect data: Start tracy-capture before running the test to avoid empty areas where nothing happens: Run the code, then upload the collected data to the viewer. You'll see something like this: Are those are GC pauses we're looking at? 🤔 You really should go read the official manual. Yes, BEFORE you run into corrupted memory, surprising grouppings, or otherwise botched profiling runs.