Thats a good point. Um. maybe thats swap is whaat is happening. Though I dont think that we are swapping, that would makes the most sense. Below are our 9 memcached servers 1. how much free ram as listed by free -m 2. memcached version number 3. how much ram is being used by memcached right now, its near full again (full at 1GB)
https://gist.github.com/e886d958a4bc8e103810 Right now we it doesnt appear that we have swapping. However, we do run our memcached instances on the same slices as our app servers where our mongrels live. Perhaps spikes in mongrels is causing it to swap.. Do those free numbers look good? >From what Ive been told is that the second row of free is more important.. -/+ buffers/cache: XXX XXX Thats how much actual free ram we have before we start swapping A gig on each slice seems o-plenty. Thanks again for all the helpful feedback and responses thus far. Tung On Mar 18, 8:04 pm, Dustin <[email protected]> wrote: > On Mar 18, 8:00 pm, tongueroo <[email protected]> wrote: > > > memcached reads are reported as very slow. 10+ seconds. > > Are you giving it more RAM than you actually have? I would expect > that behavior if it were fetching from swap.
