memcached and streaming
dustin at spy.net
Mon Feb 4 07:55:42 UTC 2008
On Feb 3, 2008, at 23:05, dormando wrote:
>> ...And binary protocol got rid of mget, because everyone is supposed
>> to go streaming ;).
> ... we'd need to use it to refactor the binary tree to not write
> packets for mget. This is one of my major concerns for the binary tree
> as-is, but I've had no time to really figure it out. While cork/nopush
> should give us the desired effect of coalescing packets, we'll still
> save significant performance (especially on the BSD's) if we can
> the syscalls down some.
I'm using all the iov stuff assuming it will do the right thing.
What it does not do, however, is explicitly state that the server
should stop and then start transmitting.
Basically, the reception of the first silent get should cork, and the
next command that isn't silent should uncork.
More information about the memcached