What's the plan and timetable to fix Thunderbird performance at startup due to Lightning bugs and flaws

Magnus Melin mkmelin+mozilla at iki.fi
Thu Jul 18 17:57:14 UTC 2019

On 18-07-2019 18:40, Wayne Mery wrote:
> On 7/18/2019 7:05 AM, Magnus Melin wrote:
>> Performance improvements are indeed high on the priority list. The 
>> first step will be to get some tests for UI performance so that we 
>> can measure what progress we make (and don't regress). We should have 
>> some of these later this year.
> Why should tests block fixing bugs, which in some cases prevent users 
> from using Calendar, or keep users on an older version 
> Thunderbird/Calendar?
They don't need to wait, I'm just saying that with tests it's much more 
easy to see if the changes have the desired effect.

> And are you suggesting we need to make the switch to ical.js 
> <https://bugzilla.mozilla.org/show_bug.cgi?id=978570> before making 
> further tweaks?
Not really. We want to make ical.js performant enough to replace libical 
by 76 (preffed on by default) and drop libical shortly after. But to 
make sure it actually is performant enough, tests would be helpful.

>> Like you noticed, there are many individual smaller things that can 
>> add up, and there's generally no magic bullet to just it all fixed at 
>> once.  OTOH, there are some larger topics like making proper use of 
>> multiple processes, process per tab like Firefox, that have potential 
>> to speed things up significantly. I don't have detailed timetable for 
>> that, though I'm hoping we can get there in 1-2 ESR releases.
> You're not suggesting not waiting 1-2 ESR to fix perf improvements 
> that don't require multiprocess, correct?
All improvements are of course welcome to land as soon as someone comes 
up with them.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/tb-planning/attachments/20190718/862f4719/attachment-0001.html>

More information about the tb-planning mailing list