tracing: revisit perf implication of many trace tags
Aperta
area/perf
area/tracing
help wanted
- Lingua principale
- C++
- Stelle
- 28.9k
- Fork
- 5.6k
- Merge medio
- 1g 20h
- PR unite (30g)
- 437
Descrizione
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.
Guida per i contributori
Apri la guida per i contributori
Valutazione
Questa issue non è ancora stata valutata.