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.

Thanks,
Wendy

Reply via email to