profiling
profiling copied to clipboard
aclysma
Provides a very thin abstraction over instrumented profiling crates like puffin, optick, tracy, and superluminal-perf.
When `[build-dependencies]` use `profiling` it can cause trouble building the target crate. If possible I'm looking for advice and updates that could be made to the documentation. ## Background Recently...
Would it be reasonable to expose the colors in this crate? It would enhance the `tracy` backend experience quite a bit. For example, in https://github.com/gfx-rs/wgpu-rs/discussions/879 we would mark every crate...
When using profiling from multiple libraries and 2 binaries, all within the same workspace, I'm getting the following error in the libraries: ```rust error[E0433]: failed to resolve: could not find...
The additional scope break some clippy lint detection (like `missing_errors_doc`) This Fix #75 WIP: the change affect only when no profiling instrumentation is enabled. But if the puffin (by example)...
Use of #[profiling::function] shouldn't break Clippy lint detection like [`missing_errors_doc`](https://rust-lang.github.io/rust-clippy/master/index.html#missing_errors_doc). Currently, this report no lint ```rust /// This `profiling::function` attribute is equivalent to profiling::scope!(function_name) #[profiling::function] fn some_function() -> Result{ burn_time(5)?;...
this https://github.com/aclysma/profiling/blob/master/profiling-procmacros/src/lib.rs#L79C38-L80C75 ``` let calling_info = format!("{}: {}", struct_name, func.sig.ident); ``` Can be a bit redundant if most tracing is in the same file. Perhaps ways to configure the name?...
The WGPU project uses `profiling` for debugging, and speaking as a maintainer of it, it's been lovely. Thank you so much for this crate! We wanted to give back by...
async functions may resume and continue execution any time. This crate currently does not account for this in any way. For example, this: ```rust use std::time::Duration; use tracing_subscriber::layer::SubscriberExt; fn main()...
