prometheus-community
scaling & ideas for reducing connection count
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%?
That breaks if there's multiple scrapers, all active clients should have a connection.
On Fri 27 Dec 2019, 00:31 John Belmonte, [email protected] wrote:
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%?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/RobustPerception/PushProx/issues/70?email_source=notifications&email_token=ABWJG5XFDV5Y4TUFZGFRPYDQ2VEEVA5CNFSM4J7SQLRKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICY7CVQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABWJG5TVIC6NILV6QQUJS2LQ2VEEVANCNFSM4J7SQLRA .
