Looks like we should leave cachedump until we come up with an official alternative (or just leave it alone as is?).
Apart from that, people seem to not speak out for 'maps' and 'malloc' subcommands... does anyone on the list have any thoughts for them? Toru On Sun, Feb 1, 2009 at 7:22 PM, dormando <dorma...@rydia.net> wrote: > > I think some clients have been developed around the cachedump command... > Okay maybe just the FUSE client, but I caught someone trying to use that > in prod at *least* once... > > It's more user friendly as a command that pulls a subset of the data. If > it were to be modified and brought in as an official command, it would at > least need an argument to specify a limit. Otherwise those "quick" > debugging routines would require a massive datadump you'd then have to > trawl through. > > I'm still convinced a full dump command will be abused more than it's > worth, but I forget where we left off last on that debate. > > -Dormando > > On Wed, 28 Jan 2009, Toru Maesaka wrote: > >> >> Hi, >> >> 'stats maps' imho, isn't so useful since we can get the same information >> with commands like ldd(1). This doesn't need to be in the server since >> low layer folks that are interested in this information would know what >> to do to obtain this information. >> >> 'stats malloc', would be useful for debugging the slabber but you do >> have a point, it doesn't need to be in memcached. The actual useful >> information is provided with 'stats slabs'. >> >> 'stats cachedump', ASFAIK is not an officially supported subcommand. >> As in, it is not stated 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 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 slabs will give detailed info for the slab allocation). >> > I believe that getting detailed information about the malloc implementation >> > doesn't belong in the memcached protocol, but you should be able to use >> > other tools on your system to monitor this. >> > >> > stats maps - I don't think this belongs in the protocol (and I have no idea >> > what you would use the output to in a deployed scenario). There are plenty >> > of tools available on different platforms that would give you more info.. >> > >> > So.. Are people using these features and would you be extremely sad if we >> > removed them from the next version of memcached. >> > >> > 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. >> > >> > So what does people think? >> > >> > Trond >> > >> > >> >
