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
We currently (upcoming 0.14) have a Sender which uses an unbounded channel for outgoing messages. This doesn't provide any back pressure to the send function in case we are unable to process the messages quickly enough, possibly leading to OOM conditions.
A fairly straight forward way to solve this would be to limit the buffer size of the channel (See buffer indocumentation). This does mean that the sender needs to use send and .await over it as appropriate, requiring all send-related functions to be async This would mean an impactful API overhaul, but it would in my view be worthwhile.
The text was updated successfully, but these errors were encountered:
udoprog
changed the title
Make send and associated functions async functions
Make send and associated send_* functions async
Dec 29, 2019
We currently (upcoming 0.14) have a Sender which uses an unbounded channel for outgoing messages. This doesn't provide any back pressure to the send function in case we are unable to process the messages quickly enough, possibly leading to OOM conditions.
A fairly straight forward way to solve this would be to limit the buffer size of the channel (See
buffer
indocumentation). This does mean that the sender needs to usesend
and.await
over it as appropriate, requiring all send-related functions to beasync
This would mean an impactful API overhaul, but it would in my view be worthwhile.The text was updated successfully, but these errors were encountered: