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
* feat: add message byte batching
Adds a new setting `minSendBytes` that is `undefined` by default.
If `undefined` all messages sent through multiplexed streams will
be serialized and sent over the wire immediately.
If set to a number, it will be used as a byte value, and the
serialized bytes of all messages sent during the current tick will
be buffered up to that value.
Once either the buffer lengths hits that value or the next tick
begins, all bytes in the buffer will be sent over the wire.
* chore: add readme note
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,6 +71,7 @@ Creates a factory that can be used to create new muxers.
71
71
72
72
-`maxMsgSize` - a number that defines how large mplex data messages can be in bytes, if messages are larger than this they will be sent as multiple messages (default: 1048576 - e.g. 1MB)
73
73
-`maxUnprocessedMessageQueueSize` - a number that limits the size of the unprocessed input buffer (default: 4194304 - e.g. 4MB)
74
+
-`minSendBytes` - if set, message bytes from the current tick will be batched up to this amount before being yielded by the muxer source, unless the next tick begins in which case all available bytes will be yielded
74
75
-`maxInboundStreams` - a number that defines how many incoming streams are allowed per connection (default: 1024)
75
76
-`maxOutboundStreams` - a number that defines how many outgoing streams are allowed per connection (default: 1024)
76
77
-`maxStreamBufferSize` - a number that defines how large the message buffer is allowed to grow (default: 1024 \* 1024 \* 4 - e.g. 4MB)
0 commit comments