Motivation: Allow to configure the maximum number of messages to write per eventloop run. This can be useful to ensure we read data in a timely manner and not let writes dominate the CPU time. This is especially useful in protocols like QUIC where you need to read "fast enough" as otherwise you may not read the ACKs fast enough. Modifications: - Add new ChannelOption / config that allows to limit the number of messages to write per eventloop run. - Respect this setting for DatagramChannels Result: Reduce the risk of having WRITES block the processing of other events in a timely manner Co-authored-by: terrarier2111 <58695553+terrarier2111@users.noreply.github.com> |
||
---|---|---|
.. | ||
src | ||
pom.xml |