* Amos Jeffries <squid3@xxxxxxxxxxxxx>: > The Squid HTTP Proxy team is very pleased to announce the availability > of the Squid-3.2.2 release! I tried 3.2.2 in the same setup as 3.1.21 - same machine, same settings, starting with an empty cache_dir. While 3.2.2 was working flawlessly during the morning hours (up to about 10:30 in the morning), we encountered performance issues when approaching noon. The average service time skyrocketed from a normal average of 40ms to about 350ms and users were reporting huge delays. But why? Are there known performance issues with 3.2? We're using 4 idential servers in a cluster here, so it's relatively easy to reproduce. -- Ralf Hildebrandt Charite Universitätsmedizin Berlin ralf.hildebrandt@xxxxxxxxxx Campus Benjamin Franklin http://www.charite.de Hindenburgdamm 30, 12203 Berlin Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
