> On Tue, Feb 28, 2012 at 10:02 AM, Wendy Cheng <[email protected]> wrote: > > On Tue, Feb 28, 2012 at 9:47 AM, Wendy Cheng <[email protected]> > > wrote: > >> Does anyone have a ballpark number for "memslap --server <name> > >> --test=set" command ? Somehow I got ~0.6 seconds that is surprising. > >> Intuitively, our network round-trip latency for 16K tcp data is less > >> than 0.001 second. I expected the memslap "set" command would not go > >> up to msec range (?). Our lab machines are 8-cpu+2926.412 mhz+12GB > >> memory with 100gb ethernet. All configurations (memcached-1.4.10 + > >> libmemcached-1.0.2) use default setting. > >> > >> We're not in the tuning stage yet but would like to know beforehand if > >> this number is expected. > >> > > > > Oops .. my bad :) .. memslap runs 10000 loops on default .. so one > > single "set" must run around 0.000068 s (68 usec) (?). > > > > > To make it clear, we're happy with the number *now*... Too bad that I > can' t recall this post. Sorry for the interruption !
You might want to consider mc-crusher as well. https://github.com/dormando/mc-crusher it's still rough, but from what it can do it's very flexible.
