tracing: revisit perf implication of many trace tags
Open
area/perf
area/tracing
help wanted
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 428
Description
We have an increasing amount of trace tags that we emit without any configuration. We should try to profile the cost of doing these tags, especially if there is no tracing configured (null tracer). We should potentially allow for the emitted tags to be configured in high perf scenarios.
Contributor guide
Assessment
This issue has not been assessed yet.