Re: healthy ratio of Qcache_hits to Qcache_inserts?

[Jeff Ambrosino]

This is a web application, and for each user's request (hit), there are essentially two SELECTS:

1) a SELECT to a Session table with a session ID, and the Session record is updated each request -- this is obviously going to have 0% cache hit.
2) a SELECT to a lookup table that contains a key with < 10 values -- this is the one I'm concerned with, as it should have near 100% cache hit rate.

The tricky thing is I don't have an easy way to see which SELECTS are hitting the cache and which aren't. Is there a way to inspect MySQL's query cache to see what's in there and what's getting hit?

thanks
JB