This link has been bookmarked by 103 people . It was first bookmarked on 01 Jun 2007, by Ken Wei.
-
27 Sep 11
-
21 Oct 10
-
15 Sep 10
-
16 Jun 10
-
05 Apr 10
-
03 Mar 10
-
27 Aug 09
-
20 May 09
-
17 May 09
-
08 May 09
-
04 May 09
-
18 Apr 09
-
25 Mar 09
-
16 Dec 08
-
12 Dec 08
-
08 Dec 08
-
02 Dec 08
-
17 Nov 08
-
26 Jul 08
-
11 Jul 08
-
27 Jun 08
-
03 Jun 08
-
13 May 08
-
03 May 08
-
11 Apr 08
-
Memcached has long been the answer to most questions containing the word scale. There are some spectacular memcached installations out there. Facebook is said to run a 200 server with 3TB of memory solely for servicing memcached; Shopify, twitter, digg, Slashdot and just about every other public facing application depends on it. Facebook’s installation is said to deliver a 99% cache hit rate while servicing tens of thousands of requests a second.
There are many ways to use this elaborate hash table and many ways which are more trouble then they are worth. In our experience the key to use memcached effectively is to ask it for the exact thing you want, but i’m getting ahead of myself.
-
-
16 Feb 08
-
18 Jan 08
-
16 Dec 07
-
15 Dec 07
-
16 Nov 07
-
15 Nov 07
-
22 Oct 07
-
16 Oct 07
-
20 Sep 07
-
15 Jun 07
-
-
01 Jun 07
-
In Shopify we use this technology as a way to do Page caching. We keep the rendered HTML, HTTP return status code and Content-Type in memcached and use all the differentiating input variables as keys such as content of the shopping cart. We keep the HTML because this saves our server cluster valuable bandwidth by avoiding loading and compiling the liquid templates from the NFS server. Requests for cached documents are now rendered in sub 10ms regions.
-
-
28 May 07
-
27 May 07
-
26 May 07
-
25 May 07
-
24 May 07
-
23 May 07
-
-
22 May 07
Chris GrantSome great insight into how to best use memcache.
memcached rails performance ruby memcache programming cache caching
-
M GUse versioning of collections
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.