The estimated CPU usage is inaccurate in short connections with low concurrency
Open
Nobody has claimed this yet.
bug
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
- Deploy TiProxy on cloud and they are labelled with zones
- Start a workload with 10 long connections and short connections with 20 concurrency
2. What did you expect to see? (Required)
TiProxy always route to local backends
3. What did you see instead (Required)
TiProxy routes 30% traffic to remote backends
4. What is your version? (Required)
master
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 reproducing the reported workload: deploy TiProxy on zone-labelled cloud backends, then run 10 long connections alongside short connections at 20 concurrency. Compare the expected all-local routing with the observed 30% remote traffic; the issue names no source file or test, so identify the routing or CPU-estimation entry point before defining the regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100