Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep-alive strategies for connections in connection pool #791

Open
weissi opened this issue Dec 6, 2024 · 0 comments
Open

Keep-alive strategies for connections in connection pool #791

weissi opened this issue Dec 6, 2024 · 0 comments

Comments

@weissi
Copy link
Contributor

weissi commented Dec 6, 2024

Much like grpc-swift already does, in large deployments it's often important to make sure that the HTTP client has for example 1,000 connections ready to go straight away.

Currently, we can't force 1,000 connections to be pre-opened (one problem) but even if we allow AHC to open 1k connections and make it open 1k connections by just creating enough traffic, AHC will close them again. After the idleTimer expires. And we can't just raise the idleTimer to say 8 hours because that usually triggers TCP inactivity timeouts so the connections will be cut from elsewhere.

AHC should support different keep-alive strategies such as:

  • TCP keepalives
  • sending a HEAD / request once every 5 mins or so
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant