I think Moxi processes items in batches already and not one by one. At least it reads all the items on the socket, then processes them, and get back to the socket, I don t know if you mean the same thing by "They did say they focused on batching together lots of operations over individual item latency"
How did you contact twitter guys? It could be nice to ask them directly my questions. Cheers Nico 2012/7/6 Dustin <[email protected]> > > On Thursday, June 28, 2012 2:15:43 AM UTC-7, Nicolas Motte wrote: >> >> Is there anyone who tried to use Twemproxy? >> It's an open-source proxy for memcached provided by Twitter. >> It says "Proxy the complete memcached ASCII protocol", what about the >> binary protocol? >> >> I m looking for a comparison with Moxi. >> > > I can't speak for the project, but when I talked to the guys at twitter > about it it sounded like it might be a bit less of a generally applicable > thing than moxi. That is, moxi tries to be a proxy for any kind of > upstream or downstream, and twemproxy is focused on the things that twitter > needed to make their own applications perform better. Many of those things > may help your applications. They did say they focused on batching together > lots of operations over individual item latency. > > Hopefully someone from the team can add more clarity (or tell me I'm > completely wrong). >
