You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now all reads/writes allocate a buffer whenever they happen. This can be quite expensive and it'd probably be more useful to pool buffers between operations. For example the event loop could have a cache of buffers which are handed out on reads/writes.
Probably want to benchmark the impact before/after as well.
The text was updated successfully, but these errors were encountered:
This adds a cache of buffers to be stored locally on the selector for new
requests to use for both reads and writes. The cache has a maximum size of the
number of buffers it can store and new buffers are allocated if the cache is
empty at the time.
Closestokio-rs#245
This adds a cache of buffers to be stored locally on the selector for new
requests to use for both reads and writes. The cache has a maximum size of the
number of buffers it can store and new buffers are allocated if the cache is
empty at the time.
Closestokio-rs#245
This adds a cache of buffers to be stored locally on the selector for new
requests to use for both reads and writes. The cache has a maximum size of the
number of buffers it can store and new buffers are allocated if the cache is
empty at the time.
Closestokio-rs#245
Conflicts:
src/sys/windows/mod.rs
src/sys/windows/selector.rs
src/sys/windows/tcp.rs
src/sys/windows/udp.rs
Right now all reads/writes allocate a buffer whenever they happen. This can be quite expensive and it'd probably be more useful to pool buffers between operations. For example the event loop could have a cache of buffers which are handed out on reads/writes.
Probably want to benchmark the impact before/after as well.
The text was updated successfully, but these errors were encountered: