Hey Denny and Nath; The other thing you'd do in dev mode, is to run it in non-daemon mode with -v and it'll spit out all the logging. That'll include hits, misses and keys.
Matta On 22/08/2011, at 11:08 PM, Nathan de Vries wrote: > While Matt is correct that memcached should be treated as a black box, it's > actually quite feasible (and reasonable!) to want to look at what it's > storing. You'll often need this during development, but also on occasion when > a live server is running amok. > > There's a couple of tools you'll want to check out: > > https://github.com/fauna/peep > https://github.com/andrewfromcali/mcinsight > > The former attaches to a running process, freezes it, inspects the key > metadata, and returns the process to a running state (via dtrace). It's > suitable for use in development & production. > > The latter acts as a proxy for your memcached server and captures keys data > on the way through. It's really only something you'd want to use in > development. > > > Cheers, > > Nathan de Vries > > On Monday, 22 August 2011 at 8:02 PM, Matt Allen wrote: > >> Hi Denny; >> >> You can't. Generally you'll be using some sort of known, reproducible >> composite key to retrieve the data you need. >> >> An example of this that i've used in the past for some fragment caching is a >> combination of model class name + id or controller name + model + id. >> >> Hope that helps, >> Matta >> >> >> On 22/08/2011, at 6:16 PM, Denny wrote: >> >>> Hi, all >>> >>> As we all know, we can use cache in our application. Here is question: >>> >>> How can I get all the key and value in memcache database? >>> >>> 1. in console, do we have a method to list all? >>> 2. can we directly visit memcache database for this? >>> >>> -- >>> Denny >>> Sent with Sparrow >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Ruby or Rails Oceania" group. >>> To post to this group, send email to rails-oceania@googlegroups.com. >>> To unsubscribe from this group, send email to >>> rails-oceania+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/rails-oceania?hl=en. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby or Rails Oceania" group. >> To post to this group, send email to rails-oceania@googlegroups.com. >> To unsubscribe from this group, send email to >> rails-oceania+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/rails-oceania?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to rails-oceania@googlegroups.com. > To unsubscribe from this group, send email to > rails-oceania+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-oceania@googlegroups.com. To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
