HEX
Server: Apache/2.4.18 (Ubuntu)
System: Linux phubuntu06.apexhosting.com 4.4.0-210-generic #242-Ubuntu SMP Fri Apr 16 09:57:56 UTC 2021 x86_64
User: master06 (1000)
PHP: 7.0.33-0ubuntu0.16.04.16
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,
Upload Files
File: //usr/share/webmin/squid/help/edit_delay.html
<header>Delay Pools</header>
<p>
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.
<p>
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.
<p>
<b>Initial bucket level</b>
<br>
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 <b>max</b> values are very large (the max value when configuring limits actually applies to the bucket size for the pool).