Re: [squid-users] Delay Pool

From: Henrik Nordstrom <hno@dont-contact.us>
Date: Wed, 20 Apr 2005 08:25:34 +0200 (CEST)

On Wed, 20 Apr 2005, Wennie V. Lagmay wrote:

> Thank you Henrik and Dev, I was able to configure it.
>
> acl all src 0.0.0.0/0.0.0.0
> acl ipaddr1 src 192.168.10.0/255.255.255.0
> acl ipaddr2 src 192.168.11.0/255.255.255.0

These can be joined into a single acl, simplifying things somewhat.

acl clients src 192.168.10.0/255.255.255.0 192.168.11.0/255.255.255.0

> delay_pools 1
> delay_class 1 3
> delay_access 1 allow ipaddr1
> delay_access 1 allow ipaddr2
> delay_access 1 deny all
> delay_parameters 1 128000/128000 -1/-1 2000/8000
>
>
> With the above config, I'm telling that the total bandwidth is 1Mbps, per IP
> block has no limit and per IP address have a commited rate of 16kbps (when
> the network is busy) and 64 kbps (when the network is not busy).

This is not exacly what the above says.

What it says is that each client gets a committed rate of 16 kbps (2000
bytes/s) with a credit of 8000 bytes allowing them to download burts of
up to 8000 bytes without delay after being idle.

This is not related to the traffic level of other cliets. Only when the
higher levels (network or global) runs short is the client limited by
other traffic.

but other than this it looks like a reasonable configuration.

> objective is for every client to have 64000 bits of bandwidth but as the
> number of clients grows it will decrease to 16000bits but it is guaranteed.

I would probably use a somewhat bigger pool size to give the impression of
this. Maybe 80000 or 160000.

How fast connection do the clients have to the proxy?

Regards
Henrik
Received on Wed Apr 20 2005 - 00:25:44 MDT

This archive was generated by hypermail pre-2.1.9 : Sun May 01 2005 - 12:00:04 MDT