Re: stalled transfers (performance problem?)

Barrie Spence wrote:

> > Sounds like a stalled TCP connection between Squid and the origin
> > server. If Squid has a ongoing connection to the origin server,
> > then any additional clients who requests the same object reuses
> > this connection.
>
> What about multiple connections from the same browser? Neither of
> the squids I'm playing with ever handle much more than my local
> client.

The same applies to restarted requests until Squid discovers that the
provious request is truly aborted, which in 1.2beta does not happen
untill data is flowing.

> Unfortunately, I can't say what's happening off my local network,
> but the stalled transfers are more obvious with squid than the
> existing Netscape proxy. Even the data transfer rates are low
> (often < 3kb/s - alternatively, via the Netscape proxy > 50kb/s
> is typical).

Yes. Stalled transfers should be more obvious when using Squid than
other proxies. The difference is that Squid reuses ongoing requests for
the same object, while most other (including Netscape) always starts a
new request for the object.

---
Henrik Nordström
Sparetime Squid Hacker