envoyproxy/envoy

tracing: revisit perf implication of many trace tags

Open

#9,653 opened on Jan 10, 2020

View on GitHub
 (0 comments) (1 reaction) (0 assignees)C++ (5,373 forks)batch import
area/perfarea/tracinghelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

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

Research direction
Profile the cost of trace tags in a null tracer scenario and identify potential configuration options to reduce overhead.
Tech stack
cpp
Domain
performanceobservability
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++Profiling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40