On 5/01/2016 4:11 p.m., Alex Samad wrote:
> On 5 January 2016 at 12:40, Amos Jeffries wrote:
>> What the above does is not limit any particular user. But limits the
>> total server bandwidth to those domains (combined) to 10Mbps. It is a
>> good solution, but still has a few problems.
>>
>> WU wil
On 5 January 2016 at 12:40, Amos Jeffries wrote:
> What the above does is not limit any particular user. But limits the
> total server bandwidth to those domains (combined) to 10Mbps. It is a
> good solution, but still has a few problems.
>
> WU will now be very slow, proportional to how many user
On 5/01/2016 1:38 p.m., Alex Samad wrote:
> So thought I would try it out
>
> #
> # Delay Pools
> # http://wiki.squid-cache.org/Features/DelayPools
> #
> http://www.serverwatch.com/tutorials/article.php/3357241/Reining-in-Bandwidth-With-Squid-Proxying.htm
> delay_pools 1
> delay_class 1 1
>
> #
So thought I would try it out
#
# Delay Pools
# http://wiki.squid-cache.org/Features/DelayPools
#
http://www.serverwatch.com/tutorials/article.php/3357241/Reining-in-Bandwidth-With-Squid-Proxying.htm
delay_pools 1
delay_class 1 1
# 10Mb/s fille rate , 20Mb/s reserve
# 10485760/8 = 1310720
# 2097
Hi
Just wanted to confirm my understanding of delay pools and the ability
to ratelimit inbound traffic.
Today one of our W10 machines did it windows update .. New patch ..
.MS SQL SP3 - 384M big patch
So it contacts our squid proxy with then downloaded it from WSUS
update ... which is geocached
