Open
Bug 685884
Opened 13 years ago
Updated 9 years ago
Lazily initialize calendar items from their components
Categories
(Calendar :: Internal Components, defect, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: Fallen, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf, Whiteboard: [patchlove])
Attachments
(1 file)
|
(deleted),
patch
|
Details | Diff | Splinter Review |
While working on bug 678343, I found that parsing a calIIcalComponent into the javascript objects we use in calEvent/calTodo costs around 30 ms on my machine. This of course adds up with a lot of events and causes UI freeze. I have some work in progress code that takes care, but its not quite ready yet. Using this bug for tracking.
|
||
Updated•13 years ago
|
Severity: normal → major
|
Reporter | |
Comment 1•10 years ago
|
||
I *think* this is the patch I referenced. Not quite sure. Its far from ready yet. Attaching so it doesn't get lost. Anyone is invited to pick up this patch!
|
|
Reporter | |
Updated•10 years ago
|
Priority: -- → P2
|
|
Reporter | |
Updated•10 years ago
|
Priority: P2 → P3
|
|
||
Comment 3•9 years ago
|
||
This would help startup performance, eg bug 487832 ?
Flags: needinfo?(philipp)
OS: Linux → All
Whiteboard: [patchlove]
|
|
Reporter | |
Comment 4•9 years ago
|
||
I'm sure it will, constructing items now takes 30-40ms, with this patch we could cut it down to the minimum, e.g. 10-20ms.
Flags: needinfo?(philipp)
|
|
||
Updated•9 years ago
|
Blocks: tb-startupperf
You need to log in
before you can comment on or make changes to this bug.
Description
•