860114 - [meta] slow content process startup when parent is busy

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Performance, defect, P4)

Description

[Gregor Wagner [:gwagner]]

If the parent process is busy and we get an incoming call we end up spending a ton of time requesting required information in sync calls from the parent during child startup.
We should avoid this and send all required info when we launch the process or try to not block on these calls.

This bug tracks findings.

Comment 1

[Justin Lebar (not reading bugmail)]

What is the parent process busy doing?

At some level we rely on the parent process to do lots of setup for a call; if it's busy, the call will take longer to connect than it should, regardless of whether the child blocks on the parent or not.

Comment 2

[Dave Huseby [:huseby]]

Is this still a bug?  Is this a class bug with Bug 860097 just one example of how to fix this?  Can you give us some more information on this?

Comment 3

[Gregor Wagner [:gwagner]]

(In reply to Dave Huseby [:huseby] from comment #2)
> Is this still a bug?  Is this a class bug with Bug 860097 just one example
> of how to fix this?  Can you give us some more information on this?

Our current process launching procedure is not optimal. When we create a child process, we are requesting values from the parent. Some of those calls are sync calls and if the parent is busy with other stuff that initialization can take some time.

The solution is to package all information that is needed for initialization with the start-up call so we don't need any additional information from the parent.

Comment 4

[BMO Automation]

Firefox OS is not being worked on