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.

Sign up for GitHub

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

Jump to bottom

[FEATURE REQ] Use higher default connection pool limit for calls originating from SDK on .NET Framework. #15207

Closed
kasobol-msft opened this issue Sep 16, 2020 · 0 comments · Fixed by #15263
Closed

[FEATURE REQ] Use higher default connection pool limit for calls originating from SDK on .NET Framework. #15207

kasobol-msft opened this issue Sep 16, 2020 · 0 comments · Fixed by #15263
Assignees
@pakrym
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@kasobol-msft
Copy link
Contributor

Library or service name.
Azure.Core

Is your feature request related to a problem? Please describe.

Context:
The ask originates from Storage SDK but is applicable elsewhere.
Our customers who are using .NET Framework in multi-threaded application are often facing an issue that default connection pool is small (2 or 10). This manifests as timeouts or large perceived latency for some population of requests.
Currently we advise customers to bump default connection pool limit at ServicePointManager. However, we're looking for providing better customer experience out of the box.

Feature request:
Find a way to apply different default connection pool limit by default if call is originating from the SDK than .NET FX dictates.
As well as set this default reasonably high (20? 50?).
We should also find a way to configure pool limit just for the SDK calls.

Related
#9087
#14929
#12975
@jsquire jsquire added Client This issue points to a problem in the data-plane of the library. needs-team-triage Workflow: This issue needs the team to triage. labels Sep 16, 2020
@AlexGhiondea AlexGhiondea added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that and removed needs-team-triage Workflow: This issue needs the team to triage. labels Sep 16, 2020
@pakrym pakrym mentioned this issue Sep 18, 2020
Merged
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-net that referenced this issue Jul 15, 2021
@msyyc
CodeGen from PR 15207 in Azure/azure-rest-api-specs
4d2d1d3 
Deviceprovisiongservices t1 config (Azure#15207)

* sql t2 readme config

* readme config

* Update readme.python.md

* conflient resolve

* t1 revert

* Update readme.python.md

Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com>
@github-actions github-actions bot locked and limited conversation to collaborators Mar 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pakrym pakrym

Labels
Azure.Core Client This issue points to a problem in the data-plane of the library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Increase connection pool size limit automatically pakrym/azure-sdk-for-net
4 participants
@jsquire @pakrym @AlexGhiondea @kasobol-msft