You'll run into a few problems... -m 1 won't work the way you think since
it'll force-allocate one slab page per slab class. we don't have a
fallback mode to cut that down.
We also don't do anything to detune the thread stack size (which is
probably 2mb still?), plus a handful of allocations around each worker
thread (the new event base, connection buffers, etc).
That still seems sort of high, but thread stacks + etc would account for
quite a bit of it. You can also try reducing the size of the hash table..
that could show up as VSZ if you haven't written anything into it yet.
> --
>
> ---
> You received this message because you are subscribed to the Google Groups "memcached" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
memcached+...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.
>
>