On Thu, Mar 1, 2012 at 5:55 PM, Wendy Cheng <[email protected]> wrote: > Hi, > > We plan to start tuning work for our Memcached setup. The binaries > were built on top of "engine_pu" branch (storage engine interface). A > quick test run (everything on default, including storage engine > itself) using > > "/usr/local/bin/memslap --server xyz --test=get --concurrency=1024" > > got a bunch of "Failured on read " errors. Using "gdb" to dig a little > bit, nothing in "default_get()" shows failure. Before we continue the > trace tomorrow, if folks can pass some tuning tips (particularly > around the network stacks), it'll be greatly appreciated. >
Reply to my own post :) ... It looks like a client (memslap) issue. Just did a quick try on two clients, both up to 800 concurrency. They runs thru w/out troubles. Digging into the issue now. -- Wendy
