prometheus-community / prometheus-community/PushProx
scaling & ideas for reducing connection count
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 811
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
has anyone yet measured how many connections a pushprox process can handle?
same for a typical load balancer like GLB which may be put in front of multiple pushprox instances-- how much in resources with the load balancer consume given the persistent connections?
I wonder if the pushprox client can use a heuristic to reduce the connection time of /poll. For example, don't initial /poll unless half of the recently observed scrape period has elapsed. That could reduce global connection count by 50%?
Contributor guide
No contributing guide indexed for this repository
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 measuring how many persistent connections a PushProx process and a GLB load balancer can handle. Then inspect the /poll behavior and evaluate whether delaying the initial poll based on the observed scrape period is viable. Done means documented resource measurements and a clear decision on whether to pursue the heuristic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100