Memory management
Steven Grimm
sgrimm at facebook.com
Sun Mar 25 18:35:20 UTC 2007
That tool appears to be rounding the slab sizes in its output. They are
not the same size. Run memcached -vv and you'll see the actual sizes
(they're printed at startup time when you run with -vv).
-Steve
rkmr.em at gmail.com wrote:
> This is my memcached slab details. Why are there multiple 1kB, 2kB
> slabs? Seems ineffective. Is there someway I can change it?
> thanks
>
> memcached-tool 127.0.0.1 <http://127.0.0.1>
> # Item_Size Max_age 1MB_pages Full?
> 6 252 B 179013 s 1 no
> 7 316 B 171928 s 1 no
> 8 396 B 180061 s 1 no
> 9 496 B 183877 s 1 no
> 10 620 B 183887 s 1 no
> 11 776 B 183707 s 1 no
> 12 972 B 178798 s 1 no
> 13 1 kB 170944 s 1 no
> 14 1 kB 167250 s 1 no
> 15 1 kB 167223 s 1 no
> 16 2 kB 181903 s 1 no
> 17 2 kB 169914 s 1 no
>
>
> On 3/25/07, *Steven Grimm* <sgrimm at facebook.com
> <mailto:sgrimm at facebook.com>> wrote:
>
> Slab sizes -- or rather, the sizes of the items in each particular
> class
> of slabs -- are fixed at startup. Can you give an example of the
> kind of
> fragmentation you're seeing (or expecting to see)?
>
> -Steve
>
>
> Jure Petrovic wrote:
> > Hello,
> >
> > a question about slabs.
> >
> > Does Memcached have the ability to change slab sizes during
> runtime in
> > order to reduce internal fragmentation?
> >
> > Thank you,
> > Jure Petrovic
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.danga.com/pipermail/memcached/attachments/20070325/0e9913ec/attachment.html
More information about the memcached
mailing list