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

On 19/03/11 10:44, david_at_lang.hm wrote:
> On Fri, 18 Mar 2011, Amos Jeffries wrote:
>
>> On 18/03/11 21:54, david_at_lang.hm wrote:
>>> On Fri, 18 Mar 2011, Amos Jeffries wrote:
>>>
>> <snip>
>>>> Some are offset by optimizations and fixes later, so its not
>>>> cut-n-dry. Work is underway by Alex and Co. to identify the problems.
>>>> We all work on ways to grab performance back when found. Most of these
>>>> optimizations won't make it into 3.1, but 3.2 hopes to be better.
>>>
>>> any feel for how 3.2 is doing (how close is it to no longer being
>>> 'release candidate', which for some strange reason scares management
>>> types ;-)
>>
>> So far its looking like no earlier than end-April.
>>
>> FWIW we have some selective 3.2 builds running happily in production.
>> They just need a bit of testing before use.
>
> thanks, this helps a lot, I didn't know if it was 'probably sometime in
> the next few weeks' or 'possibly sometime in 2012'
>
> April timeframe gives me a lot of useful information.
>
> what areas are still being worked on?

  * "RockStore" shared cache for efficient SMP caching support.
  * Comm layer restructuring for IPv6 split-stack support
  * miscellaneous Bugs (34 important ones left today)

  libecap 0.2.0 support and the final expected cache manager SMP changes
hit 3.2 yesterday.

>
> In my case I specifically just need the access control portion, so if
> some caching modes are still showing bugs it wouldn't affect me, but if
> SMP configurations are still having bugs it would.

I'm not aware of anything major in SMP. Just the hassle of each worker
currently needing its own separate cache.

There are some crashes in auth, but with patches available to avoid that
(not merged due to inefficiency).

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.11
   Beta testers wanted for 3.2.0.5