Closed Bug 355454 Opened 15 years ago Closed 15 years ago

Scalability: Slow startup with large remote calendars

Categories

(Calendar :: Provider: ICS/WebDAV, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: FelixWiemannBugs, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060507 Mozilla Sunbird/0.3a2

Sunbird and Lightning 0.3a2 take about ten seconds to start up if I subscribe to a large remote calendar like <http://info.vassar.edu/calendar/calendars/campuscalendar.ics>.  That's too long, it impacts the usability.  It happens at every startup, and both Sunbird and Thunderbird are unresponsive while the calendar loads.

Reproducible: Always
Component: General → Provider: ICS/Webdav
OS: Linux → All
QA Contact: general → ics-provider
Hardware: PC → All
Whiteboard: [qa discussion needed]
Using this build: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.4pre) Gecko/20070328 Calendar/0.5pre

I don't see that this calendar is unusable.  We also tried it in a recent Lightning nightly.  I recommend that you take a look at the 0.5pre nightly builds, and see what you think.  Many performance improvements have been made.

There is still more that can be done, but I think for a calendar of this size, it is Ok for now.  

Marking as WFM.  If we can determine specific bottlenecks to performance with large calendars, I would welcome specific bugs for those.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Whiteboard: [qa discussion needed]
The performance is still the same with the current code from CVS.  Time to start end terminate Sunbird with the Vassar calendar on 600 MHz:

user    0m19.733s
sys     0m0.824s

And without the calendar:

user    0m4.888s
sys     0m0.972s

Anyway, I'm not sure if there is anything you *can* do about this.  Just wanted to let you know.
You need to log in before you can comment on or make changes to this bug.