4 ms·
This could work ... if you only have one machine on your local network and your outbound link can sustain that data rate 24/7. It's not really a practical solu
by jbri 16y ago
This could work ... if you only have one machine on your local network and your outbound link can sustain that data rate 24/7.
It's not really a practical solution for 99% of cases.
- ugh 16y agoWouldn’t it be an improvement even with those caveats?
- jbri 16y agoBest case would be your router/modem dropping/ECNing packets to keep below that cap, which would fix the "multiple computers" issue. You've still got the problem of buffering in your ISP's network screwing you up if it can't handle the rate you're requesting (as well as not being able to take advantage of the extra speed when it's less congested), but there's really nothing you can do on your end about that. Yes, hard-capping your outbound traffic would help, but it's not a "solution" by any means.
- akira2501 16y agoYou do the egress shaping at the router, not on each individual machine. And you shape the entire interface, not individual traffic flows. As far as jitter in the outgoing rate, that's what the buffer is there for. What shaping helps you avoid is: a) filling the buffer and those side-effects and b) prematurely filling the buffer at a high rate while the rest runs at a low rate.
- jbri 16y agoThe problem isn't the buffer being full, it's a problem with the buffer being <em>large and full</em>. Buffering less and just dropping packets when your smaller buffer fills (or even before then) lets the congestion control stuff do its work.
- akira2501 16y agoI've been doing this in my home networks for years, and this is exactly what egress shaping does for me. The local router drops packets, the internal clients back off.
- regularfry 16y agoYou could (in fact, should) put the egress filter in the router. Given that there isn't a practical solution for 99% of cases, this is worth considering.