Sent from my iPhone.
On Thu, Apr 1, 2010 at 9:37 PM, James Golick <firstname.lastname@example.org>
Well, folks, I'm feeling a little stupid right now (adding to the injury inflicted by one Mr. Stump :-P).
So, here's the story. The cache hit rate is up around 97% now. The ruby code is down to around 20-25ms to multiget the 20 rows. I did some profiling, though, and realized that a lot of time was being spent in thrift. Turns out, that's where pretty much all the time was going.
I just ran the same test using java (scala) and the load is taking around 2-4ms.
That's with the binary accelerated thrift for ruby?