On Sat, 26 Feb 2005, Dinil Divakaran wrote:
It would have been better if the squid manipulated its receiver window to manage the downloading rate.
This is in effect what happens, but it has to fill up first.
If you look at a packet trace of a delayed response via Squid you will see
1. Starts out at the default window size (OS controlled)
2. When the delay pool kicks in the window size rapidly shrinks, and only the configured bytes per second is forwarded.
That way it need receive only the required amount of bytes per second (as specified by the delay pool parameters.) This also will put a bound on delay.
Delay pools deliver a specific rate per second, with a optional initial window where no limit is applied.
Manipulating the receive window alone only changes how effective TCP is over high latency links.
Regards Henrik
