-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blocked streams under heavy load #69
Comments
which protocol version are you using, 1 or 2? |
if we've reached the bandwidth limit,then:
|
I'm using version 1. It's not only that the buffer is full, the whole connection state becomes undefined. I'll try with version 2. Let's see how it behaves under my traffic conditions. |
Tested the following:
Adaptive peer window makes the difference. I'll test a bit more with version 2. Many thanks! |
smux starts blocking/dropping segments when under heavy load.
When forwarding rate is below my link rate (>100 Mbps) everything is fine.
Once the rate goes above 100 Mbps, smux starts to block exisitng and new streams.
This applies to client and to server role.
I've spent too much time with tracing and debugging my code and finally decided
to switch back to yamux. Problem disappeared immediatelly.
Please support.
The text was updated successfully, but these errors were encountered: