<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Re: Largest production memcached install?</TITLE>
<META content="MSHTML 5.00.2919.6307" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=595073718-03052007>With
the configuration you noted below, what is your CPU utilization. We are
implementing memcached in our environment and I am trying to get a feel for what
we will need for production. I realize that it all depends on how we are
using it, but I am interested to see what it is based on your
configuration.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=595073718-03052007></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=595073718-03052007>Thanks,</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=595073718-03052007></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=595073718-03052007>Jerry</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN
class=595073718-03052007></SPAN></FONT> </DIV>
<BLOCKQUOTE>
<DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
memcached-bounces@lists.danga.com
[mailto:memcached-bounces@lists.danga.com]<B>On Behalf Of </B>Steve
Grimm<BR><B>Sent:</B> Thursday, May 03, 2007 11:33 AM<BR><B>To:</B> Sam
Lavery; memcached@lists.danga.com<BR><B>Subject:</B> Re: Largest production
memcached install?<BR><BR></DIV></FONT><FONT
face="Verdana, Helvetica, Arial"><SPAN style="FONT-SIZE: 12px">No clue if
we’re the largest installation, but Facebook has roughly 200 dedicated
memcached servers in its production environment, plus a small number of others
for development and so on. A few of those 200 are hot spares. They are all
16GB 4-core AMD64 boxes, just because that’s where the price/performance sweet
spot is for us right now (though it looks like 32GB boxes are getting more
economical lately, so I suspect we’ll roll out some of those this
year.)<BR><BR>We have a home-built management and monitoring system that keeps
track of all our servers, both memcached and other custom backend stuff. Some
of our other backend services are written memcached-style with fully
interchangeable instances; for such services, the monitoring system knows how
to take a hot spare and swap it into place when a live server has a failure.
When one of our memcached servers dies, a replacement is always up and running
in under a minute.<BR><BR>All our services use a unified database-backed
configuration scheme which has a Web front-end we use for manual operations
like adding servers to handle increased load. Unfortunately that management
and configuration system is highly tailored to our particular environment, but
I expect you could accomplish something similar on the monitoring side using
Nagios or another such app.<BR><BR>All that said, I agree with the earlier
comment on this list: start small to get some experience running memcached in
a production environment. It’s easy enough to expand later once you have
appropriate expertise and code in place to make things run
smoothly.<BR><BR>-Steve<BR><BR><BR>On 5/3/07 8:06 AM, "Sam Lavery"
<sam.lavery@gmail.com> wrote:<BR><BR></SPAN></FONT>
<BLOCKQUOTE><FONT face="Verdana, Helvetica, Arial"><SPAN
style="FONT-SIZE: 12px">Does anyone know what the largest installation of
memcached currently is? I'm considering putting it on 100+
machines(solaris/mod_perl), and would love to hear any tips people have for
managing a group of that size(and larger). Additionally, are there any
particular patches I should try out for this specific platform?
<BR> <BR> <BR>Thanks in
advance,<BR>Sam<BR> <BR> <BR> <BR><BR></SPAN></FONT></BLOCKQUOTE><FONT
face="Verdana, Helvetica, Arial"><SPAN
style="FONT-SIZE: 12px"><BR></BLOCKQUOTE></SPAN></FONT></BODY></HTML>