You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 22, 2020. It is now read-only.
Currently the Client class creates a new HttpClient per request, which means a new connection as well.
For high load scenarios, the object allocation and round trip cost is too high, so the Client class should contain a single httpclient and manage its lifecycle.
This would also create the requirement to ensure the class behaves in a threadsafe way, so we can create a single client and share it across multiple indexing threads.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the Client class creates a new HttpClient per request, which means a new connection as well.
For high load scenarios, the object allocation and round trip cost is too high, so the Client class should contain a single httpclient and manage its lifecycle.
This would also create the requirement to ensure the class behaves in a threadsafe way, so we can create a single client and share it across multiple indexing threads.
The text was updated successfully, but these errors were encountered: