Skip to content

Commit

Permalink
Do not enable fibers in tracing-tracy
Browse files Browse the repository at this point in the history
Fibers introduce a significant overhead to each invocation of Tracy
instrumentation calls, which in turn makes all tracing instrumentation
points (with callstack collection disabled) 2x slower than they could
be.

I anticipate that `fibers` still may become unconditional requirement in
the future due to #35, but there's no reason to impose that overhead on
users today.
  • Loading branch information
nagisa committed Jun 11, 2022
1 parent a4cb0d1 commit 1db8d5a
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion tracing-tracy/Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ bench = true
[dependencies]
tracing-core = { version = "0.1", default-features = false, features = ["std"] }
tracing-subscriber = { version = "0.3", default-features = false, features = ["fmt", "registry"] }
client = { package = "tracy-client", path = "../tracy-client", version = "0.13.0", default-features = false, features = ["fibers"] }
client = { package = "tracy-client", path = "../tracy-client", version = "0.13.0", default-features = false }

[dev-dependencies]
tracing = { version = "0.1", default-features = false, features = ["std"] }
Expand Down

0 comments on commit 1db8d5a

Please sign in to comment.