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 have a bunch of logic intended to try to keep queue contents when a program changes the queue depth. This is silly.
Normally this is only done when the socket is first created. This is extra complexity that is not needed.
Furthermore, the new queue size might be smaller anyway, so queue contents can be dropped as a result of that. And generally any of the queues are in "best effort" cases anyway, where it is perfectly fine to drop messages on the floor.
The text was updated successfully, but these errors were encountered:
We have a bunch of logic intended to try to keep queue contents when a program changes the queue depth. This is silly.
Normally this is only done when the socket is first created. This is extra complexity that is not needed.
Furthermore, the new queue size might be smaller anyway, so queue contents can be dropped as a result of that. And generally any of the queues are in "best effort" cases anyway, where it is perfectly fine to drop messages on the floor.
The text was updated successfully, but these errors were encountered: