subcommands in memcached, and
personally I would like to kill some of them (I believe that they have
nothing to do in memcached):
stats malloc - What would you use the output of this command for?? the
biggest malloc user is the slab allocator, but that always allocates 1MB
chunks.. (and stats
in the protocol document. I think we can say that
it is safe to remove an undocumented command.
My two cents :)
Toru
On Wed, Jan 28, 2009 at 5:39 PM, Trond Norbye trond.nor...@sun.com wrote:
Hi,
I have been looking at some of the stats subcommands in memcached, and
personally I
Josh Snyder wrote:
My next question is stats cachedump. Are people using that feature??
Personally I would like to kill that as a stats subcommand, and try to think
of a better way we may help developers to try to debug their application.
stats cachedump can be very helpful. Here's how
My next question is stats cachedump. Are people using that feature??
Personally I would like to kill that as a stats subcommand, and try to
think
of a better way we may help developers to try to debug their application.
stats cachedump can be very helpful. Here's how we use it (albeit
Hi,
I have been looking at some of the stats subcommands in memcached, and
personally I would like to kill some of them (I believe that they have
nothing to do in memcached):
stats malloc - What would you use the output of this command for?? the
biggest malloc user is the slab allocator
My next question is stats cachedump. Are people using that feature??
Personally I would like to kill that as a stats subcommand, and try to think
of a better way we may help developers to try to debug their application.
stats cachedump can be very helpful. Here's how we use it (albeit
