setMulti implementation for Java client?

[Kevin Burton]

About a month ago  I benchmarked the Java client implementation.

I noticed that using 1 getMulti instead of 1000 individual gets yielded 
a BIG performance improvement (which of course makes a lot of sense).

The problem is that in my cache implementation I needed to do a lot of 
individual sets and since there was no setMulti implementation I was 
actually seeing that my memcached implementation was 8x slower than my 
native mysql only implementation.

I'm trying to build a cache for our Torque OM layer (which has since 
been tricked out and I'd like to OSS some day) where our objects would 
be kept in memcached but with the current individual put implementation 
it was about 8x SLOWER ...

Anyway.. If there aren't any plans for this I might end up implementing it.

Kevin

-- 


Use Rojo (RSS/Atom aggregator)! - visit http://rojo.com. 
See irc.freenode.net #rojo if you want to chat.

Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html

   Kevin A. Burton, Location - San Francisco, CA
      AIM/YIM - sfburtonator,  Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412