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.
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.
-Magnus
_______________________________________________ tb-planning mailing list tb-pl...@mozilla.org https://mail.mozilla.org/listinfo/tb-planning
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?
And are you suggesting we need to make the switch
to ical.js before making further tweaks?
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?
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 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.
-Magnus
Date: Thu, 18 Jul 2019 14:05:18 +0300
From: Magnus Melin <mkmelin...@iki.fi>
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.
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.
Date: Thu, 18 Jul 2019 14:05:18 +0300
From: Magnus Melin <mkmelin...@iki.fi>
Performance improvements are indeed high on the priority list.It is good to hear about it, Thunderbird team should communicate more regularly in details about plans to tackle performance issues, maybe via a dedicated blog posts perhaps? Just a suggestion...
Date: Thu, 18 Jul 2019 14:05:18 +0300
From: Magnus Melin <mkmelin...@iki.fi>
Performance improvements are indeed high on the priority list.
Blank profile - From startup till main UI appears
TB 78.6.1 https://share.firefox.dev/2Ntqk8f
TB 85.0b3 https://share.firefox.dev/2Y5s1uo
IMAP email only (all network calendar disabled) - From startup till first email can be read
TB 78.6.1 https://share.firefox.dev/398G3C6
TB 85.0b3 https://share.firefox.dev/3sMXvnn
IMAP email + calendar (cache enabled) - From startup till first email can be read
TB 78.6.1 https://share.firefox.dev/39WEpSX
TB 85.0b3 https://share.firefox.dev/3qUSgQX
IMAP email + calendar (cache disabled) - From startup till 2mn30 - still not able to read my first email by then!
TB 78.6.1 https://share.firefox.dev/3c86kCt
TB 85.0b3 https://share.firefox.dev/2Y3etj7