The "STAT bytes" leveled out at 8.1GB for the 1.4.30 instance (with -C -m
10240 -I 20m -c 4096 -o modern,slab_chunk_max=1048576 -f 1.25), vs. 9.4GB
for 1.4.25, and STAT curr_items is 120k vs. 136k. So it still seems to be
making worse use of memory, but it's far better than any of the previous
what about without the slab_chunk_max change? (just bare modern) is usage
better?
could I get a stats snapshot from the one that filled?
> On Aug 13, 2016, at 9:35 AM, andr...@vimeo.com wrote:
>
> The "STAT bytes" leveled out at 8.1GB for the 1.4.30 instance (with -C -m
> 10240 -I 20m -c 4096
It's looking like slab_chunk_max of 512k will sit better as a default
until stitching is done...
It doesn't create slab classes of say (770k) that still take 1MB of space
due to the slab mover needing consistent page sizes.
It doesn't have the low end efficiency hole between 16k and ~80k slab
siz
