Hi, On Feb 18, 2013, at 7:11 PM, dormando <[email protected]> wrote:
> 1) libmemcached requests 2 keys
> 2) memcached responds with 1 key
> 3) libmemcached sends no-op packet
> 4) memcached responds with 2nd key, no-op packet
Assuming one server and binary protocol... a single write to the socket would
be made for both keys under both the binary and ascii server (assuming the keys
are small enough to fit into the default buffer, which is the case assuming
trunk version of memcached).
The code bunches up as many requests as can be made into the buffer before
flushing. When looking through the code I didn't find anything that should be
fouling that up (though I did find that we were incrementing the packet counter
more then what we should, but that won't really effect anything).
Anyway, everything looks to be ok.
Cheers,
-Brian
smime.p7s
Description: S/MIME cryptographic signature
