Anyone using Memcached with ASP.NET on a distributed farm?

Question

We have 22 HTTP servers, each of which works with separate ASP.NET caches. They are read from a read-only database that is updated only from peak hours.

We use the file dependency to invalidate the cache, asking the servers to "update" their caches ... If this is accidentally done during peak hours, it risks knocking down our database cluster due to a sudden flood of open connections.

Has anyone used memcached with ASP.NET in this distributed form? It seems to me that this will be a huge advantage: you only need to create one cache (and hit DB 21 times less), and memcached will process it in every window.

If you have one, will you put it in the same field as the HTTP mailboxes, or are you using a separate cache level? How scalable is it, can we expect it to require powerful servers? Our working dataset is not huge (we enter it in 4 gigabytes of memory on each HTTP field, just fine).

How do you deal with invalidity?

We are looking for experience and military stories.

EDIT: Win2k3, IIS6, 64-bit servers ... 4 gigabytes in a box (I think we might have upgraded it to 16 gigs when we switched to 64-bit servers).

Answer 1

"memcached would handle its distribution on each field"

memcached memcached. memcached . memcached , , , . reset .

memcached: memcached.

Answer 2

( memcached) , memcached , -, http- ( , ). 64- (, , , memcached), , memcached. , memcached, , , .

Answer 3

, .

, , - .

Memcache , asp.net , -? , . - CPU, . ( ) -.

, .

, , . , .

Answer 4

If you want to get replication on your memcached servers, it might be worth a look at repcached . This is a patch for memcached that handles part of the replication.

Answer 5

It is worth checking out Velocity , which is a distributed cache provided by Microsoft. I cannot give you a step-by-step comparison with memcached, but Velocity is integrated with ASP.NET and will continue to receive more opportunities for development and integration.