Would it be possible to stagger the timings when cache_digests are retrieved from peers?
Note: The information here is current for version 2.2. Squid already has code to spread the digest updates. The algorithm is currently controlled by a few hard-coded constants in peer_digest.c. For example, GlobDigestReqMinGap variable determines the minimum interval between two requests for a digest. You may want to try to increase the value of GlobDigestReqMinGap from 60 seconds to whatever you feel comfortable with (but it should be smaller than hour/number_of_peers, of course). Note that whatever you do, you still need to give Squid enough time and bandwidth to fetch all the digests. Depending on your environment, that bandwidth may be more or less than an ICP would require. Upcoming digest deltas (x10 smaller than the digests themselves) may be the only way to solve the “big scale” problem.
17 Interception Caching/Proxying 176 17.1 Interception caching for Solaris, SunOS, and BSD systems . . . . . . . . . . . . . . . . . . . . 177 17.1.1 Install IP Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 17.1.2 Con gure ipnat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 17.1.3 Con gure Squid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 17.2 Interception caching with Linux 2.0 and ipfwadm . . . . . . . . . . . . . . . . . . . . . . . . 178 17.3 Interception caching with Linux 2.2 and ipchains . . . . . . . . . . . . . . . . . . . . . . . . . 181 17.4 Interception caching with Linux 2.4 and net lter . . . . . . . . . . . . . . . . . . . . . . . . . 182 17.5 Interception caching with Cisco routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 17.5.1 possible bugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 1
