Well, knew I forgot something :) Just pushed a fix for that for the next
release.
You'll want to avoid setting slab_chunk_max on your own. Only adjust with
-I, and you can see the state of -I via the "item_size_max" stat in there.
Also, for what it's worth: Your `-m 8` may use more than 8
Hi,
I updated the release notes to be a little more clear. You use the -I
option, don't touch slab_chunk_max at all unless you really know what
you're doing.
All you have to do is:
-I 2m
ie:
-I 2m -o modern
... and you have a modern startup option with a 2m item limit.
On Fri, 15 Jul 2016,
with /usr/local/bin/memcached -d -m 8 -l 127.0.0.1 -p 11211 -c 2048 -b 2048
-R 200 -t 4 -n 72 -f 1.25 -u nobody -o
slab_reassign,slab_automove,slab_chunk_max=16384 -P
/var/run/memcached/memached1.pid
stats output as
echo stats settings | nc 127.0.0.1 11211
STAT maxbytes 8388608
STAT
sorry that was stats, here's settings output
memcached-tool 127.0.0.1:11211 settings
#127.0.0.1:11211 Field Value
auth_enabled_sasl no
binding_protocol auto-negotiate
cas_enabled yes
chunk_size 72
detail_enabled
any tools or command line available to get the slab_chunk_max size in
1.4.29 ?
memcached-tools doesn't see any in settings probably needs an update ?
memcached-tool 127.0.0.1:11211 stats
#127.0.0.1:11211 Field Value
accepting_conns 1
auth_cmds
ah units in KB so
-o slab_chunk_max=2048
?
how is it passed on command line with modern flag too ?
-o modern,slab_chunk_max=2048
??
On Friday, July 15, 2016 at 11:06:35 PM UTC+10, Centmin Mod George Liu
wrote:
>
> so to clarify if i want to raise max item size to 2MB i'd set -o
>
so to clarify if i want to raise max item size to 2MB i'd set -o
slab_chunk_max=2097152 ?
On Thursday, July 14, 2016 at 10:08:49 AM UTC+10, Dormando wrote:
>
> https://github.com/memcached/memcached/wiki/ReleaseNotes1429
>
> enjoy.
>
--
---
You received this message because you are
