Re: Delay Pools Setup

> Thanks for the helpful discussion on delay pools previously. This is
> what I am implementing:
>
> # acl for dialup users:
> acl localdelayed 203.22.103.1-203.22.103.127/255.255.255.255
>
> # apply class2 delay pools:
> delay_class2_access allow localdelayed

make sure you have delay_class1_access deny all

> # set the overall bucket size to 64kb (we have a 512k link so this is
> the max)
> delay_class2_aggregate_max 64000
>
> # fill the bucket at 64kb per second
> delay_class2_aggregate_restore 64000
>
> # set a larger max bucket size (16kb) so that web pages etc should be
> faster
> delay_class2_individual_max 16000
>
> # limit any downloads after this to 8kb per second
> # - modem/64k ISDN users shouldn't notice any speed degradation as
> they
> # can't download faster than this (well, forgetting compression)
> delay_class2_individual_restore 8000
>
> Any comments?
>
> A few things I'm unsure about:
> 1. To what extent does the 16kb bucket size actually make short
> downloads faster? Won't the modem still be the bottle neck?

Yes; setting the bucket size large and the throughput small
(eg, 64kb bucket and 4000 restore) means that people doing long
downloads are penalised but people doing casual browsing won't
notice any slowdown; but of course it still can't be faster than
the modem speed.
 
> 2. How can I remove the aggregate settings totally? I don't care about
> the aggregate bucket, at least for the moment. squid.conf recommends
> setting aggregate_restore to -1 but what about aggregate_max?

squid just checks that the restore is -1 and then ignores it; set both
to -1 if you want to be careful.

> 3. How is the acl defined here different to a subnet definition, say
> 203.22.103.0/255.255.255.128?

203.22.103.0/255.255.255.128 is how I would define it; they're just
different ways of writing the same thing.

David.
Received on Thu Nov 19 1998 - 20:29:09 MST