Michael Johnson dea91e94d6 Re-add the "frame" span for tracy comparisons (#8362) ... # Objective In https://github.com/bevyengine/bevy/pull/6503 there were two changes to the top level tracing span "frame. Firstly it was renamed to "main app" and secondly the scope was reduced to *only* the main app. This means that there is no longer a top level span that can be used to compare frame times. In addition to making it easier to compare across versions again, it also helps when running without the render feature. Previously the "frame" span was present in both cases but now to compare "headless" and render the comparison is between "main app" and "winit event_handler" and Tracy doesn't handle comparing non-matching frames well. Before (0.9)  After (0.10)  ## Solution This PR reintroduces the "frame" span so comparisons across versions and features is again easy.   ### Alternative As an alternative route, the `tracy-client` crate that is used by `tracing-tracy` supports the ability to set multiple "Frame" markers using the `secondary_mark_frame` function. It may be possible to create a PR for `tracing-tracy` that exposes that functionality and then publish an "update" frame marker instead. This might have additional benefits in the future as it could be used for other systems we might want to track as frames without endless nesting.		2023-04-25 14:56:05 +00:00
..
src	Re-add the "frame" span for tracy comparisons (#8362)	2023-04-25 14:56:05 +00:00
Cargo.toml	chore: Release (#7920)	2023-03-06 05:13:36 +00:00