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
{{ message }}
This repository has been archived by the owner on Apr 5, 2022. It is now read-only.
Right now, when an global outbound queue goes from empty to non-empty, every fd on remote pipes is made writable (even if only one is necessary to send the frame).
One tradeoff that could be considered is to only enable 1/N of the fds, and then set a timer to fire in some short time period (few hundred ms?) to enable the next 1/N. This timer would get cancelled if the queue went empty again.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, when an global outbound queue goes from empty to non-empty, every fd on remote pipes is made writable (even if only one is necessary to send the frame).
One tradeoff that could be considered is to only enable 1/N of the fds, and then set a timer to fire in some short time period (few hundred ms?) to enable the next 1/N. This timer would get cancelled if the queue went empty again.
The text was updated successfully, but these errors were encountered: