I'm assuming (although I don't know for sure) that unless there is another client to yield to then it won't as there's no benefit in doing so. Perhaps if you launched a number of clients that all made requests at the same time then that might be a more realistic test. Also, see how the behavior varies, if at all, when doing a multiget of ten keys vs. ten sequential gets on the same keys for example. Just a thought.
Paul On Wed, Feb 9, 2011 at 3:51 AM, Sebastian Llabres <[email protected]>wrote: > > > On Tue, Jan 25, 2011 at 4:42 PM, Paul Gale <[email protected]> wrote: > >> For local verification purposes you could always set the value of -R on >> the command line to be lower than its default of 20 (unless it latches at >> that value) as well as set the value of -t to be set to 1 or 2 perhaps >> (default is 4). >> >> >> >What is the R limit exactly? >> Please clarify: are you asking what it's value is or what behavior it >> governs or something else? >> >> Thanks, >> Paul >> >> > What the value means? I, wrongly it seems, assumed that if I set the R > value to 1, then sending a multiget with more than 1 get would cause a > connection yield. This turned out not to be the case. So I guess I'm > asking what behaviour it governs. > > Thanks for the replies! >
