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
Why we can not customize encode/decode buffer size when initializing a new reader or writer through a function argument.
NSQ use snappy for its message encode/decode with one connection one snappy encoder/decoder. This will consume more and more memory according to the connections number as each connection will use 64KB memory.
Also, this is more friendly for uses cases where the uncompressed data are almost all in small size.
The text was updated successfully, but these errors were encountered:
Why we can not customize encode/decode buffer size when initializing a new reader or writer through a function argument.
NSQ use snappy for its message encode/decode with one connection one snappy encoder/decoder. This will consume more and more memory according to the connections number as each connection will use 64KB memory.
Also, this is more friendly for uses cases where the uncompressed data are almost all in small size.
The text was updated successfully, but these errors were encountered: