You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over in https://github.com/microsoft/openvmm we use tracing heavily for all of our logging. We care a lot about binary size for one of our binaries, openvmm-hcl. Updating the workspace from tracing-core 0.1.30 to 0.1.31, with no other changes, results in roughly 300kb of additional .text binary size when compiled with our shipping profile (fat LTO, 1 codegen unit). I suspect this is due to #2555 from looking at the release notes, but am not 100% certain. The results on v0.1.33 are unchanged from v0.1.31.
Bug Report
Version
tracing 0.1.37
tracing-attributes 0.1.27
tracing-core 0.1.30
tracing-log 0.1.4
tracing-log 0.2.0
tracing-serde 0.1.3
tracing-subscriber 0.3.18
Crates
tracing-core 0.1.31
Description
Over in https://github.com/microsoft/openvmm we use tracing heavily for all of our logging. We care a lot about binary size for one of our binaries, openvmm-hcl. Updating the workspace from tracing-core 0.1.30 to 0.1.31, with no other changes, results in roughly 300kb of additional .text binary size when compiled with our shipping profile (fat LTO, 1 codegen unit). I suspect this is due to #2555 from looking at the release notes, but am not 100% certain. The results on v0.1.33 are unchanged from v0.1.31.
Repro Steps
cargo bloat -p openvmm_hcl --target x86_64-unknown-linux-musl --profile underhill-ship
to measure the baselinecargo update -p tracing-core --precise 0.1.31
to updatecargo bloat -p openvmm_hcl --target x86_64-unknown-linux-musl --profile underhill-ship
again to measure the regressionExample outputs
Before
After
The text was updated successfully, but these errors were encountered: