Squid_ The Definitive Guide - Duane Wessels [204]
Each pair of numbers specifies the fill rate and maximum bucket size. The fill rate should not be larger than the maximum size. The units are number of bytes. Thus, if you are thinking in terms of bits per second, you must divide by 8 to get bytes per second. For example, if you want to define a bucket that refills at a rate of 100 Kbits/sec, and holds no more than 300 Kbits (3 seconds) of traffic, you would write 12500/37500.
Syntax
delay_parameters pool-number
aggr-rate/aggr-max [ind-rate/ind-max [net-
rate/net-max]]
Default
No default
Example
delay_parameters 2 16000/32000 4000/8000
Related
delay_pools, delay_class, delay_access, delay_initial_bucket_level
Name
delay_initial_bucket_level
Synopsis
This directive determines the amount of traffic that Squid puts into newly created buckets. A bucket is created when Squid starts up or is reconfigured. For class 2 and 3 pools, individual and network buckets are created upon the first client request that uses the bucket. The delay_initial_bucket_level value is a percentage of the bucket's maximum size.
Syntax
delay_initial_bucket_level percent
Default
delay_initial_bucket_level 50
Example
delay_initial_bucket_level 100
Related
delay_pools, delay_class, delay_access, delay_parameters
Name
incoming_icp_average
Synopsis
This directive controls the low-level routines that periodically check the ICP socket for incoming queries and replies. The algorithm is relatively complex to fully describe here. The idea is to make sure Squid checks the ICP socket frequently enough to handle the ICP load but not so often that it is a waste of time. This directive specifies the number of normal I/O events that should occur between checks to the ICP socket. A normal I/O event refers to reading from, and writing to, client- and server-side TCP sockets.
Unless you have a thorough understanding of the polling algorithms in the source code, I strongly recommend that you leave this directive set to its default value.
Syntax
incoming_icp_average number
Default
incoming_icp_average 6
Example
incoming_icp_average 20
Related
incoming_http_average, incoming_dns_average
Name
incoming_http_average
Synopsis
This directive is similar to incoming_icp_average, except that it refers to the HTTP socket with which Squid accepts new client requests. Unless you have a thorough understanding of the polling algorithms in the source code, I strongly recommend that you leave this directive set to its default value.
Syntax
incoming_http_average number
Default
incoming_http_average 4
Example
incoming_http_average 15
Related
incoming_icp_average, incoming_dns_average
Name
incoming_dns_average
Synopsis
This directive is similar to incoming_icp_average, except that it refers to the UDP socket with which Squid receives DNS responses. Unless you have a thorough understanding of the polling algorithms in the source code, I strongly recommend that you leave this directive set to its default value.
Syntax
incoming_dns_average number
Default
incoming_dns_average 4
Example
incoming_dns_average 8
Related
incoming_icp_average, incoming_http_average
Name
min_icp_poll_cnt
Synopsis
This directive controls the low-level routines that periodically check the ICP socket for incoming queries and replies. It specifies a lower limit on the number of normal I/O events that must occur between checks to the ICP socket. Unless you have a thorough understanding of the polling algorithms in the source code, I strongly recommend that you leave this directive set to its default value.
Syntax
min_icp_poll_cnt number
Default
min_icp_poll_cnt 8
Example
min_icp_poll_cnt 10
Related
incoming_icp_average
Name
min_dns_poll_cnt
Synopsis
This directive is similar to min_icp_poll_cnt, except that it applies to the UDP socket with which Squid receives DNS replies. Unless you