Dear folks,
I am using ASP.Net cache in my web application. is there any maximum
amount of concurrent access allowed for a cache. is there any bottle neck
that is possible when nearyly 100+ concurrent users are accessing the cache
--
S.Sundararajan

Sundararajan wrote:

Since Cache is thread-safe, there is of course some sort of lock
contention involved.

AFAIK the implementation uses ReaderWriterLocks, which is fine as long
as you're mostly reading data, but that doesn't really scale well if
you have many writers.

Cheers,
--
http://www.joergjooss.de
mailto:news-reply (AT) joergjooss (DOT) de

Are you using whidbey?
If not, the readwriter seems to be suffering from problems under load,
expecially if there are frequent writes.

check out
http://www.dotnet247.com/247referenc...28/140664.aspx

also, scroll down on this link ..
http://www.andymcm.com/dotnetfaq.htm#11.6

regards,
Deep


"Joerg Jooss" wrote:

Deep Kocheta wrote:

That's not the ideal scenario for Cache anyway -- it's a read-mostly
solution.

But yes, ReaderWriterLock's current implementation seems to be rather
poor, according to what Jeff Richter said in an interview on TSS.Net.

Cheers,
--
http://www.joergjooss.de
mailto:news-reply (AT) joergjooss (DOT) de