4 votesoleg shared this idea ·
This is an awesome idea, and we’re exploring a few options to make it a reality.
However, the 600 connection limit per instance should be enough for most applications if you’re reusing or closing connections. If you truly need 600 open connections you are likely to run into the 10 minute timeout per execution.
Even after we add this you will still need to be mindful of your connection management.
Keep the votes coming!
An error occurred while saving the commentoleg commented
My case is even more frustrating, my C# (pseudo)code looks like this:
And when I get 10k items in the container I start encountering all kinds of socket exceptions, failed Azure Functions, silent function fails etc. I'm using .NET Azure storage SDK 9.1.1 and it's just spawning insane amounts of connections without resuing, closing them in-time or maybe not closing at alloleg supported this idea ·