3 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• kkara commented  ·  October 23, 2011 07:18  ·  Flag as inappropriate  ·  Delete

  I would also like to see the number of allowed concurrent connections raised. I am currently using two instances of a web roles and I'm using up 4 out of 5 of my allowed connections just for the basics (session and caching). So even if I use just 2 MB of cache, I have to buy larger cache just to support one more instance...

• Bernie Cook commented  ·  June 28, 2011 06:49  ·  Flag as inappropriate  ·  Delete

  I agree, especially on the concurrent connections front. I'd like to see the maximum number of concurrent connections increased for each respective cache size. If I want to increase the number of web roles I'm running, to meet peak periods of traffic, I now have to purchase larger cache sizes only for their larger maximum concurrent connection limit. Based on the feedback I've seen it is better to use one DataCacheFactory per role rather than disposing and creating it per request.

• ShaunT commented  ·  May 12, 2011 11:30  ·  Flag as inappropriate  ·  Delete

  Actually, regions and get by tag is also needed -- otherwise, there is no way to enumerate through a collection of things. API is not useful in its current form for programmatic use.