influxdata / influxdata/influxdb
Performance of checks
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Hello!
At the company I work, we are using InfluxDB to send metrics about CPU usage of some processes. We need to have 7 checks for each process and we can have about 120 processes running at the same time.
When we have created more than 70 checks, the response times from the HTTP API are really slow, it takes about 7 seconds to create, update, or delete any check. But, it does not matter how many checks (after 70) we have, the average time is the same. Why does it happen? Is there a way to improve those response times?
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Start by reproducing the HTTP API timings with more than 70 checks, then trace the create, update, and delete paths to identify the fixed delay and document whether the response time can be improved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, databases, observability, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100