I'm testing on the live cluster, but most of the production reads are being served by the cache. It's definitely the right CF.
On Wed, Mar 31, 2010 at 8:30 AM, Jonathan Ellis <jbel...@gmail.com> wrote: > On Wed, Mar 31, 2010 at 12:01 AM, James Golick <jamesgol...@gmail.com> > wrote: > > Okay, so now my row cache hit rate jumps between 1.0, 99.5, 95.6, and > NaN. > > Seems like that stat is a little broken. > > Sounds like you aren't getting enough requests for the > getRecentHitRate to make sense. use getHits / getRequests. > > But if you aren't getting enough requests for getRecentHitRate, are > you sure you're tuning the cache on the right CF for your 35ms test? > Are you testing live? If not, what's your methodology here? > > -Jonathan >
