Re: Which projects are most important?

Hi Alex,
  I'd go for the quickest wins, to remove blockers for other work.
In that way, I'd work on 5. (non-coding task, time consuming) and 6, then 1.

Thanks for doing this (sorry for bottom-quoting but it seems the most
appropriate way to quote in this case)

  Kinkie

On Wed, Feb 15, 2012 at 6:42 PM, Alex Rousskov
<rousskov_at_measurement-factory.com> wrote:
> Hello,
>
>    I am aware of several important problems that I can help with:
>
> 1. Removing of store_table global and moving non-shared memory cache
> into its own class. It would be nice to do that before we add support
> for shared caching of large objects (#2) so that the new code can be
> isolated to shared caching areas only. However, other than new bugs,
> this project alone will not result in changes immediately visible to users.
>
>
> 2. Support for shared caching of large objects in memory and Rock store.
> Currently, the shared memory caching limit is hard-coded to 32KB and
> Rock Store maximum is configurable.
>
>
> 3. Triage bug reports related to slow loading of Rock store at startup
> and fix the problem, if any. Rock store loads cache index in disker, not
> worker processes, so the performance impact should be minimal, but
> perhaps something still needs fixing or optimizing.
>
>
> 4. Research and possibly optimize IPC exchanges between Squid kids. I
> suspect busy (but not overloaded) Squids suffer from overheads related
> to creating new UDS sockets. If that suspicion is confirmed, we may be
> able to noticeably improve performance by keeping UDS sockets
> persistent. This project may also have a positive impact on how Squid
> kids locate each other during startup and kids restarts.
>
>
> 5. Work with Kinkie to complete the performance regression investigation
> and finalize performance regression testing procedures going forward.
> Kinkie made great progress, but several critical (and hardest to get)
> data points are still missing. Doing general optimizations such as
> StringNG or IPv6 without a good performance testing framework would be
> rather foolish.
>
>
> 6. Fix libipc/libmgr linking problems.
>
>
> 7. StringNG.
>
>
> 8. IP::Address optimization/polishing to address a known performance
> regression added by IPv6 support.
>
>
> In your opinion, what are the two or three projects I should focus on
> first? Please feel free to add new items if I missed something
> important. I will try to pick one from your prioritized list.
>
>
> Thank you,
>
> Alex.
Received on Wed Feb 15 2012 - 18:16:42 MST