oleg

My feedback

  1. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Storage  ·  Flag idea as inappropriate…  ·  Admin →
    oleg shared this idea  · 
  2. 27 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Functions  ·  Flag idea as inappropriate…  ·  Admin →

    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!
    —Alex

    oleg commented  · 

    My case is even more frustrating, my C# (pseudo)code looks like this:

    await Task.WhenAll(container.GetAllBlobs().Select(blob=>blob.DownloadToFileAsync()));

    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 all

    oleg supported this idea  · 

Feedback and Knowledge Base