[squid-users] Been a long time....

[Amos Jeffries]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31/10/2014 2:52 p.m., David Hughes wrote:
> Used to install squid years ago for some projects.  Squid is an old
> friend.
> 
> Question, and beg pardon if I skew terms.
> 
> Say one has a DSL line into a home that connects to a wireless
> router that ends up with many devices connected to it.  Laptops,
> desktops, pads, phones, network capable DVD players, etc etc etc.
> A lot of circuits get created and funnelled out through the DSL
> router.  The service provide sees this and implements throttling of
> the network service.  We can see measurable dips in the service
> based on the traffic load.
> 
> Can Squid, does squid help this situation?  As in devices
> connecting to a Squid proxy server and creating what the service
> provider sees as ONE stream, instead of many?  Reducing the
> throttling potential?

For HTTP yes. For other protocols no.

Ensure that persistent connections to clients and servers is enabled
and Squid will multiples HTTP traffic as much as possible on outgoing
connections.

> 
> I know I have framed this awkwardly but hopefully this gets the
> idea across.  Can anyone offer and answer and correct my
> conceptions about how IP traffic works?

You are assuming two things that are possibly incorrect.

Firstly, that there is intentional throttling happening at all.
 - If you have a large amount of traffic on a DSL line it is more
likely to be simple network congestion.

Secondly, that it is happening based on number of connections.
 - Active throttling is more likely to be based on total bytes
transferred. It is simpler to implement for ISP and has the same
management effects.

Squid can also help somewhat with either of those situations by
caching HTTP responses and reducing the upstream HTTP bandwidth used.

The more current your Squid version the better it will be able to do
on both persistent connection re-use, caching and HTTP/1.1 bandwidth
optimizations.

Amos
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUUu59AAoJELJo5wb/XPRjn+IIAIz+sulSc4462C4p9CuN4ack
h5IM4vlaZJSshommRUqWvSZrJMVTvaw6LAUKnng/SA9ZGUYYeZpOEVL50XBHSq4E
y+8wDkBRlxmbtLvnwM2nhw2XeZMM0FB1tg2b7dQORlFZPsCzDVrYxCLy0QwpDbCa
9Drn6yj61KHUq3ihQuyYsh3aVIrszhDMI3SubxfMUSJ9MGmW7sojTAaoZBzrrian
Cz7SrUBhGBoX2eg1F8O3t6ni+flUA9tFNgohAtl88K1urD7QjbApZh8fK0xZCsZa
bXxOwZetVoJzTKMXASe8IWT9WWyi4tv7q0pXU6Xe2fwPaeXqcExJcUA1D5nE9Uo=
=yp84
-----END PGP SIGNATURE-----