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
Consider pooling AsioBuffers instead of allocating them from the heap each time one is needed. However, if an unusually large message is sent or received rarely, that pooled buffer will needlessly waste memory. The pool should somehow be smart enough to discard such unusually large buffers.
I have considered chaining fixed-size chunks to form arbitrarily-sized buffers, but AFAICT, the msgpack-c unpacker needs the message to be completely contiguous in memory.
The text was updated successfully, but these errors were encountered:
Consider pooling
AsioBuffer
s instead of allocating them from the heap each time one is needed. However, if an unusually large message is sent or received rarely, that pooled buffer will needlessly waste memory. The pool should somehow be smart enough to discard such unusually large buffers.I have considered chaining fixed-size chunks to form arbitrarily-sized buffers, but AFAICT, the msgpack-c unpacker needs the message to be completely contiguous in memory.
The text was updated successfully, but these errors were encountered: