Hello all. I'm just beginning to play with memcache, and I read
somewhere that talked about some inefficiencies with the slab
allocator. I'm not too concerned at the moment, but I was wondering
if you could help me monitor that? I've looked through some of the
basic stats and can see how much
We're using memcached-tags for an application and have started to
experience some problems with it as our datasets have grown. Things
like losing the tag - key associations, which is the whole point of
using tags.
I was wondering if anyone else out there is using memcached-tags and has
Thanks Matt. I did look a bit through the 'stats slabs' command, but
perhaps I'm not interpreting it correctly. In the most basic test,
when I put in a 100 byte object, I'm seeing a slab being created with
a chunk size of 176. However, 'stats sizes' shows me one item of
'192'. So there's part
Thanks Matt. I did look a bit through the 'stats slabs' command, but
perhaps I'm not interpreting it correctly. In the most basic test,
when I put in a 100 byte object, I'm seeing a slab being created with
a chunk size of 176. However, 'stats sizes' shows me one item of
'192'. So there's
On Dec 4, 3:32 pm, dormando dorma...@rydia.net wrote:
An item size is the value length + the key length + pointers + bytes to
store the length + CAS header + a couple terminators/misc things. I don't
have the exact item overhead offhand but will look it up and put it in the
wiki.
The
Thanks Dormando, that was perfect. My apologies Matt, you gave me the
correct information had I been running 1.4.x, but I didn't see those
stats in 1.2.8. Makes much more sense now.
Keep in mind guys, I'm not trying to disparage memcache, just trying
to make sure I understand and can track all
