Closed
Bug 337655
Opened 19 years ago
Closed 19 years ago
safe browsing makes start up time really slow
Categories
(Toolkit :: Safe Browsing, defect)
Tracking
()
RESOLVED
FIXED
Firefox 2 alpha3
People
(Reporter: tony, Assigned: tony)
References
Details
(Keywords: fixed1.8.1)
Attachments
(1 obsolete file)
Most of the startup time that safe browsing adds is in loading and evaluating JS files in a few components. We can get a significant speed improvement by having large single JS components (rather than the current approach of using the JS subscript loader) which will benefit from JS component fastload.
Comment 1•19 years ago
|
||
SafeBrowsing is now targeted at Bon Echo Alpha 3. Tony, let us know if you think you can make this target (see dev.planning)
OS: Linux → All
Target Milestone: --- → Firefox 2 alpha3
| Assignee | ||
Comment 2•19 years ago
|
||
This does two things. First, we move all the common files into nsSafeBrowserLib.js. The other modules lazily get a reference to that module and copy over references as needed.
Second, we move from JS subscript loader to #include.
Brian, do you have branch approval powers? Suggestions on who to ask (maybe after js component fastload is on branch)?
Attachment #221865 -
Flags: review?(bryner)
| Assignee | ||
Updated•19 years ago
|
Attachment #221865 -
Flags: approval-branch-1.8.1?(bryner)
| Assignee | ||
Comment 3•19 years ago
|
||
Comment on attachment 221865 [details] [diff] [review]
v1: preprocess js components
I'm going to break this into two pieces, one for toolkit and one for browser. This will just be a tracking bug.
Attachment #221865 -
Attachment is obsolete: true
Attachment #221865 -
Flags: review?(bryner)
Attachment #221865 -
Flags: approval-branch-1.8.1?(bryner)
| Assignee | ||
Comment 4•19 years ago
|
||
Initial run on SB tinderbox: 771ms
With SB on: 868-967ms (13-25%) !
| Assignee | ||
Comment 5•19 years ago
|
||
No more regression on trunk or branch.
Updated•11 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•