Developers of Sympa

[IKEDA Soji <address@concealed>]

On Thu, 24 Jan 2013 10:45:03 +0100
David Verdin <address@concealed> wrote:

<<snip>>

> > Issues NOT yet solved:

<<snip>>

> > o Slow "List of lists" page
> >    Currently WWSympa trys to load all lists.  This behavior is a big
> >    performance hit on the site with hundreds or many of lists.
> We should probably cache something here, but I don't see how. We don't 
> display a lot of things in the list of lists, so we could probably cache 
> them and save ourselves the pain to load configs. But the problem is the 
> visibility. We have two choices:
> 
> 1- either we cache the visibility result for each user and each list in 
> database. That's a lot of entries to store in DB  - and to keep up to date.
> 2- either we change the way visibility is defined. Switching to a larger 
> granularity, such as yes/no/subscribers only could probably improve 
> performances on the list of lists. The thing here, is to NOT load the 
> full lists.

I vote for 1, but I worry database might not be very reasonable
way for caching purpose: Queries are issued so frequently and DB
server and traffic can be bottle-neck.  Especially, "visibility
cache" will become so sparse: Most of cache entries are stored in
vain.

To cross over process boundary, I suppose other mechanisms such
as shread memory (e.g. Cache::FastMMap) would be used by 6.3.

> > o Codes to handle robot config parameters and config files would be
> >    refactored and improved, however, I shall not be able to finish
> >    it in this winter (if I did).
> That could be work for the 6.3. I'm working on a candidate roadmap for 
> Sympa, that I really would like to discuss with all of you.
> We, on the RENATER side, have features that we really want to implement, 
> and also features that would be great to add but are not necessary at 
> once. All this should be discussed between us. You probably have your 
> own priorities.

I see.

> > o Bi-directional layout support by CSS.
> >    My private experiment using CSSJanus showed promising result,
> >    however, slight changes on code will be nessessary.
> Mark Overmeer, with whom I'm in contact for a development of his own in 
> Sympa, suggested CSS 3.
> He also suggested a lot of desing improvements that I will discuss with you.

It seems exciting suggestion.  Improvement by CSS3 along with
concern to older UA shall be welcomed by end users.


> > o ..., etc.
> >
> >
> >> We need to find a solution fast but we have to decide what's our next
> >> step before monday: maintaining a fork or test the 6.2 upgrade. what
> >> would be your move? any good idea to share?
> > I'm all right to swich 6.2 as a release candidate.
> I will have to disagree with this proposal.
> Even if most of the work is done, I still have too much crashes on my 
> developemnt server to release a beta.
> I think I still have, with an optimistic view, at least a week worth of 
> testing / bug fixing to have a decent release candidate.

I said too much.  Of cource 6.2 is not a "release" candidate by now.

Anyway, my commits from now on will not add new features but bug fixes.


> > My planned work on 6.2 branch has almost over.  Unsolved issues above
> > would be postponed.
> You and guillaume have really done a great work on Sympa these last months!
> Once the 6.2 is in beta, we will have plenty of time to decide what 
> should be next for Sympa.
> 
> Cheers!
> 
> David

David, thank you so much for conducting release of new Sympa!

-- Soji


-- 
株式会社 コンバージョン  セキュリティ&OSSソリューション部   池田荘児
〒231-0004　神奈川県横浜市中区元浜町3-21-2 ヘリオス関内ビル7F
e-mail address@concealed  TEL 045-640-3550
http://www.conversion.co.jp/