Jørgen Austvik

My feedback

  1. 97 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

    Jørgen Austvik supported this idea  · 
  2. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Storage » General  ·  Flag idea as inappropriate…  ·  Admin →
    Jørgen Austvik shared this idea  · 
  3. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Cloud Services (Web and Worker Role) » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Jørgen Austvik shared this idea  · 
  4. 0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Jørgen Austvik shared this idea  · 
  5. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
  6. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Reservations  ·  Flag idea as inappropriate…  ·  Admin →
    Jørgen Austvik shared this idea  · 
  7. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Storage » Tables  ·  Flag idea as inappropriate…  ·  Admin →
    Jørgen Austvik shared this idea  · 
  8. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Storage » General  ·  Flag idea as inappropriate…  ·  Admin →
    Jørgen Austvik shared this idea  · 
  9. 136 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Storage » Queues  ·  Flag idea as inappropriate…  ·  Admin →
    Jørgen Austvik supported this idea  · 
  10. 257 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Storage » Queues  ·  Flag idea as inappropriate…  ·  Admin →
    Jørgen Austvik supported this idea  · 
    An error occurred while saving the comment
    Jørgen Austvik commented  · 

    On queue messages we have Put, Get, Peek, Delete, Clear and Update. Clear, Peek and Get operates on a set/batch of messages, but Put, Delete and Update only operates on one message per REST call.

    On a Azure Storage account, we can do 20k IO/Sec, and 2k IO/Sec on one partition. One queue is on one partition, so each queue is limited to 2k IO/Sec. On Azure Tables, we can do batching on elements inside the same partition to work around the 2k IO/Sec limit on the partition, but we can't do that on Put, Delete and Update queue requests, even though they are in the same partition.

    Therefore we have this feature request: Add batching support for Put, Delete and Update of queue messages to the REST API and to the Azure SDK (CloudQueue class).

Feedback and Knowledge Base