It's at least "a couple megs". It depends on how many parallel connections you have, and the typical size of your read buffers.
If you do a lot of large multi-gets, you'll use more ram than otherwise. Future releases will probably track this memory more closely? It's not hard to do. -Dormando On Fri, 20 Mar 2009, JC wrote: > > By the way, has anyone already tried to quantify in a *more > scientific* manner the actual extra memory we should let on a box to > be sure memcached won't swap ? > > I guess memcached related overhead should be proportional to the > expected number of connection and their traffic. I guess this is about > the same for the OS with its internal buffers. But I must confess that > so far, I don't know the exact multiplying factor(s) ... > > Jean-Charles > > On Mar 20, 8:36 am, Trond Norbye <trond.nor...@sun.com> wrote: > > On Mar 20, 2009, at 8:10 AM, Sudipta Banerjee wrote: > > > > > it has 8 gigs of ram and its 64 bit > > > > Compile memcached as a 64bit binary and you should be able to use as > > much memory as you want (I have tested with up to 30Gb)... Please note > > that memcached use more memory than the memory specified with -m (for > > internal buffers etc), and you should leave memory for the os and > > other processes. The last thing you want is that your server is paging > > in and out memory pages.. > > > > Cheers, > > > > Trond >
