[FEATURE REQ] Use higher default connection pool limit for calls originating from SDK on .NET Framework. #15207
Description
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.