open-telemetry / open-telemetry/opentelemetry-python
When add the pythontracing, the pressure test shows the CPU usage increased from 13% to 30%
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
I used jmeter locally to conduct stress testing on Python, targeting both cases of having and not having tracing. The stress testing results are as follows：
test performance tool：jmeter
concurrency users：10
business path：/
- Use opentelemetry-instrument start python with for stress testing, the result is as follows：
2.Start python normally without using opentelemetry-instrument for stress testing, and the results are as follows：
From the above,it can be seen that CPU consumption increases from 13% to 30% when add tracing, is this normal?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported JMeter setup: 10 concurrent users, the / business path, and runs with and without opentelemetry-instrument. Reproduce the comparison and measure CPU usage; done means establishing whether the increase from 13% to 30% is expected and documenting the findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100