Open
Bug 512799
Opened 15 years ago
Updated 2 years ago
Fastload entire XUL window
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
NEW
People
(Reporter: dietrich, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ts])
Vlad suggested that a better way than piecemeal fastloading bits like XBL and CSS, we could instead fastload the entire XUL window state.
Reporter | ||
Comment 1•15 years ago
|
||
See also bug 94199 (XBL fastload) and bug 196843 (CSS fastload).
Reporter | ||
Updated•15 years ago
|
Whiteboard: [ts]
Reporter | ||
Updated•15 years ago
|
Priority: -- → P1
Reporter | ||
Comment 2•15 years ago
|
||
Per the startup conversation yesterday, I measured the effect fastload on cold vs warm startup. This is on a MBP 2.5ghz/4gb/7200rpm.
warm startup: 200ms slower with fastload disabled
cold startup: no detectable difference
Note that if we do this, it would be nice to also consider how we can use this in a more general way -- specifically, offline app fastload. Think saving zimbra state before onload or whatever, or even just general serialization of content and layout state that we can use for session store.
Reporter | ||
Comment 4•15 years ago
|
||
same scenario as comment #2, w/ numbers for context:
warm startup, fastload enabled: ~770ms
warm startup, fastload disabled: ~920ms
cold startup, fastload enabled: 12000ms-13000ms
cold startup, fastload disabled: 12000ms-15000ms
Reporter | ||
Updated•15 years ago
|
Priority: P1 → P2
Comment 6•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•