Link | Sync upstream | MLF | Protocol efficiency | Fudge factor | IP rate | Max rate (100%) | Fractional contribution |
L1 | 644000 | 96% | 0.884433962 | 0.849056604 | 546792 | 569575 | 31.0212% |
L2 | 531000 | 96% | 0.884433962 | 0.849056604 | 450849 | 469634 | 25.5781% |
L3 | 379000 | 96% | 0.884433962 | 0.849056604 | 321792 | 335200 | 18.2563% |
L4 | 522000 | 96% | 0.884433962 | 0.849056604 | 443207 | 461674 | 25.1445% |
Totals: | 2076000 | 1762640 | 1836083 |
Ignore their test, it provides impossible results.
TCP efficiency | ||
TCP TS+IPv6 efficiency | 95.200000% | of IP PDU (ie (TCP payload ÷ PDU) fraction) |
TCP+IPv6 efficiency | 96.000000% | of IP PDU |
TCP TS+IPv4 efficiency | 96.533333% | of IP PDU |
TCP+IPv4 efficiency | 97.333333% | of IP PDU |
TCP TS+IPv6 rate | 84.198113% | of sync rate (ie (TCP payload ÷ sync rate) fraction |
TCP+IPv6 rate | 84.905660% | of sync rate |
TCP TS+IPv4 rate | 85.377358% | of sync rate |
TCP+IPv4 rate | 86.084906% | of sync rate |
@burakkucat - assuming MTU of 1500 for yourself, all the other relevant numbers will be the same as mine - ADSL2 + ATM. So I make it 894 kbps upstream maximum at 100% MLF for 1011 kbps u/s sync rate; or 858 kbps if it were at 96% like me as a more realistic value than 96% MLF. So Burakkucat is seeing at least 43% u/s rate exaggeration! Much worse than me. Perhaps my TCP test sessions are slower because TCP doesn’t work so well with four bonded lines so reduces the inherent test exaggeration.
The speedtest-cli speed tester gave a result of 9.17 / 1.81 - an almost equally unlikely upstream result; . . .
@Burakkucat - Isn’t your downstream sync rate really high just now ? Or am I just forgetting. Looks pretty good anyway.