On 09/05/2013 12:50:19 PM, Sebastian Kemper wrote: > On Mon, Sep 02, 2013 at 04:03:01PM -0500, Karl O. Pinc wrote: > > Queing input traffic is hard, since it's already got to you through > > the bottleneck of your Internet link. > > > > TCP has to "ramp up", starting slow and getting faster as more acks > > show successful receipt. If your link to the net is clogged http > > packets will rarely get through which slows up the "slow start" tcp > > model. The solution is to throttle your bandwidth _below_ that of > > your actual bandwidth. This allows "extra" "default" packets down > the > > pipe to be accepted while "bulk" packets are dropped, making the > bulk > > streams slow down and allow room in the pipe for "default" packets.
> I've throttled my up- and download bandwidth. I had tested with > various > levels of throttling until my pings came back without lag introduced > by > my ISP's queuing. So I guess I'm good in that department. It would be interesting to know, given the bandwdith you've got, just how much you've had to discard in order to get this behavior. > Maybe :) But I'd really love to see how things behave if the bulk > traffic actually made it into the correct downstream bucket (1:40). Sorry, I didn't actually look at your config and it's not something I can pay attention right now. Karl <[email protected]> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein _______________________________________________ openwrt-users mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
