Software: Apache/2.2.3 (CentOS). PHP/5.1.6 

uname -a: Linux mx-ll-110-164-51-230.static.3bb.co.th 2.6.18-194.el5PAE #1 SMP Fri Apr 2 15:37:44
EDT 2010 i686 

uid=48(apache) gid=48(apache) groups=48(apache) 

Safe-mode: OFF (not secure)

/usr/libexec/webmin/squid/help/   drwxr-xr-x
Free 50.88 GB of 127.8 GB (39.81%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     edit_delay.html (942 B)      -rw-r--r--

Delay pools provides a means a restrict bandwidth usage of clients. With delay pools, clients can be restricted at the individual level, or in groups. ACLs are used to apply bandwidth limits to users.

This page displays any existing pools, and their limits. Also, there is a section for global options, which at this time only has one option.

Initial bucket level
Because of the way delay pools work, a new client could potentially be permitted to use more than their fair share of bandwidth because their new bucket would be empty. In a congested network, this would mean that other connections from clients with nearly full buckets would be starved of bandwidth for some period of time. This option defaults to 50%, and can likely be left alone, unless your max values are very large (the max value when configuring limits actually applies to the bucket size for the pool).