Open
Bug 835681
Opened 12 years ago
Updated 2 years ago
Remove the sync messages from BrowserElementChild startup
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
NEW
People
(Reporter: cjones, Unassigned)
References
Details
(Keywords: perf)
Attachments
(1 file)
1.66 KB,
patch
|
Details | Diff | Splinter Review |
Looking at
http://people.mozilla.com/~bgirard/cleopatra/#report=427594015c91a5fedfa918262af7c4767efa68c5
the sync messages in _init() are consuming a lot of the profile. By my analysis so far, I don't think they're real overhead, but they're very distracting and in a different factoring of the startup code, they could become real overhead.
Reporter | ||
Comment 1•12 years ago
|
||
Not a serious patch, just for testing purposes.
With these changes, the stopwatch timing of startup doesn't seem to change (at least I can't measure a difference) which is expected, but we do have happy times: an idle event loop during early startup waiting for OnInputStreamReady()!
Reporter | ||
Comment 2•12 years ago
|
||
Aha! The idle event loop is actually an async-sync wait on the b2g process, to return an fd for the application.zip.
So if we pre-open() and send over the application.zip fd, we'll actually reduce real work and should see a win.
Updated•12 years ago
|
Component: DOM: Apps → DOM: Mozilla Extensions
Reporter | ||
Comment 3•12 years ago
|
||
(I know you're occupied with other work, but) do you have a proposal for how to avoid these messages?
Flags: needinfo?(justin.lebar+bug)
Comment 4•12 years ago
|
||
I was thinking we'd just send a blob of properties when the child starts up. A simple hack would be to set some properties somewhere and then just read them out later. Perhaps we could use prefs for this (using the knowledge that they won't be forwarded up to the parent)? Otherwise it's simple to add a service.
Flags: needinfo?(justin.lebar+bug)
Reporter | ||
Comment 5•12 years ago
|
||
frame scripts can ask nsITabChild for things, in a not too terribly gross way (IIRC).
Comment 6•12 years ago
|
||
bug 835698 comment 54 implies we should eventually fix this here for a nice startup perf boost. So asking for at least tracking here.
Updated•12 years ago
|
tracking-b2g18:
--- → ?
Updated•12 years ago
|
status-b2g18:
--- → affected
Assignee | ||
Updated•12 years ago
|
Component: DOM: Mozilla Extensions → DOM
Updated•6 years ago
|
Priority: -- → P3
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•