-
Notifications
You must be signed in to change notification settings - Fork 130
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
Performance issues at 300 MBit/s #101
Comments
I effectively have the same situation over a pair of adsl lines (seeing significantly less bandwidth than I expect). I'm currently wondering if this has anything to do with DUP'd ACK's (see #100). But - any other ideas welcome |
Hello Mark, interestingly, there is talk about using different network cards in the other issue. So long, |
Yeah - the more we can rule out, the better :-) |
Wich mlvpn version do you use? |
Master + a couple of minor mods of my own |
I should have tagged a name in my question, it was for @Manawyrm initially :) |
I'm using mlvpn version 2.1.2. And yes, I seem to have dup ACKs, Out-of-Order, Segment not captured and all of that, too. |
Hi,
I have two lines:
docsis -> 200 / 25 Mbit/s
vdsl -> 100 / 40 Mbit/s
The aggregation site has a Gigabit NIC and can reach full speeds to (and from) both lines.
My server configuration looks like this:
and the client configuration is this:
Now, the problem is, that when downloading:
VDSL 100 gets 100 MBit/s traffic,
DOCSIS 200 gets only 100 MBit/s traffic, too.
In total 200 Mbit/s only, not 300.
Same story with the upload speed, ~40 MBit/s total max.
I can't surpass the maximum speed of a single link.
I have tried to change many of the parameters.
Setting bandwidth_upload on the server and on the client side has had no effect (that I could observe).
Maybe setting some more extreme values here could lead to a change?
I also manipulated the reorder_buffer_size parameter, I tried using 0, 64, 128 and 256.
Both sides have powerful CPUs and are not limiting in either CPU time or interrupts.
What could I try to get this to work properly?
Thanks,
Tobias
The text was updated successfully, but these errors were encountered: