Re: [squid-users] performance drop moving from 3.0 to 3.1?

On Fri, 18 Mar 2011, david_at_lang.hm wrote:

> On Fri, 18 Mar 2011, Amos Jeffries wrote:
>
>> On 18/03/11 10:05, david_at_lang.hm wrote:
>>> ping, any comments on this?
>>>
>>> excluding acl's, cache_peer* and *direct config entries (~500 lines
>>> worth, all IP, servername, port# or url_regex based)
>>
>> Tested with or without all those ACLs? They do make a difference to speed,
>> even the fast ACL tests.
>
> I would expect them to, but my issue isn't with the overall speed, but rather
> with the relative speed of the two versions when running the same ruleset. It
> appears that 3.1 is significantly slower under these conditions than 3.0.
>
>>> pid_filename /var/run/squid.pid
>>> cache_dir null /tmp
>>> client_db off
>>> cache_access_log syslog squid
>>
>> NP: Squid needs a syslog format spec. Same as you would use in the syslog
>> config. "syslog:daemon.1" or some such. And the directive name is now just
>> "access_log"

it is documented as the facility and severity being optional, and the
format spec is given 'squid'

>> There is about 30% CPU load increase as well as the raw speed drop. That
>> 30% is IMO what you are measuring. When topping out the CPU it obviously
>> can't handle many more RPS.
>>
>> * adding IPv6 support
>> - copying, checking version and text'ifying larger IPs a lot is SLOW.
>> - looking up DNS twice (AAAA and A) is relatively slower.
>> - failover when connecting via a network with broken IPv6 connectivity
>> results slower server connect times. any transit network blocking ICMPv6
>> breaks *your* IP failover.
>
> 3.1 was compiled without IPv6 support (I'll report all the config options in
> the morning)

Ok, the config options for 3.0 and 3.1 are:
Received on Fri Mar 18 2011 - 21:53:07 MDT