iproto: fix a performance bug (saves up to 10% CPU)
When selecting the next buffer to flush, take into account not just its size, but how much of it has already been flushed. This saves a couple syscalls per connection per event loop.
Loading
Please register or sign in to comment