496893 - The displaying of many alarms seems to take excessive resources

Status: RESOLVED DUPLICATE of bug 983715

(Calendar :: Alarms, defect)

Description

[Wolfgang Sourdeau]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; fr; rv:1.9.0.10) Gecko/2009042805 Iceweasel/3.0.9 (Debian-3.0.9-1)
Build Identifier: 20090608035852

When multiple alarms are displayed, it seems some kind of "batch mode" would be useful in order to reduce the time and the resources needed to display them.
For example, the display of hundreds of alarms can take at least 30 seconds to complete. Also, it seems there are places where updating alarms is resource-consuming as well.
This bug report is meant as a starting point for discussions around similar issues that people involved here could think about.

Reproducible: Always

Comment 2

[Wolfgang Sourdeau]

Problem 1:
Old alarms are reparsed at each launch, which causes a longer and longer delay.
Using a local alarm cache would probably solve that problem, as well as others

Comment 3

[Georgi D. Sotirov]

Any workaround to this bug? I'm using Calendar 1.0 pre, because I use Google Calendar as many others local and remote calendars. I have not started Sunbird for one week and now it could not start, because of the problem described here.

Comment 4

[Brian Morin]

I am not a developer, but have been having this type of problem. Sunbird works on my wifes settings, but not mine. It starts, according to the task manager, but when asked to be displayed, it indicates that there is nothing to display. Yet it takes up 96 to 100 percent of resources. 

Can someone tell me where I can go... Sorry, I mean for this problem...

Thanks in advance. 
bri

Comment 5

[Georgi D. Sotirov]

In fact, I'm not noticing this problem with Lightning extension to Thunderbird and I think Sunbird is dead as standalone application, so could this one be closed?

Comment 6

[Philipp Kewisch [:Fallen][📱📆]]

I doubt the root cause is really fixed here. We've changed nothing to improve the situation, neither in Lightning nor in Sunbird. Speed may have improved since js and dom performance has also improved in the later nightlies. I'd suggest leaving this bug open until we can improve the situation in Lightning itself.

Comment 7

[Philipp Kewisch [:Fallen][📱📆]]

We've improved (perceived) performance by making the display asynchronous in bug 983715. I think this will be fixed with that bug.