Tracy profiling in pipelined-rendering #2834
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This has already been reviewed and merged into
main
but we need it onpipelined-rendering
too for awesome profiling tools!Tracy is:
With the
trace_tracy
feature enabled, you run your bevy app and either a headless server (capture
) or a live, interactive profiler UI (Tracy
), and connect that to your bevy application to then stream the metric data and events, and save it or inspect it live/offline.Previously when I implemented the spans across systems and stages and I was trying out different profiling tools, Tracy was too unstable on macOS to use. But now, quite some months later, it is working stably with Tracy 0.7.8. You can see timelines, aggregate statistics of mean system/stage execution times, and much more. It's very useful!
tracing-tracy
crate which supports our tracing spanstrace_tracy
for consistency with othertrace*
featuresObjective
Solution