Ting-Yu Chou [:ting] (away) Reporter
	Description • 10 years ago

Currently the application.zip is inflated in child process after it receives the fd from parent (either through OpenFileAndSendFDRunnable or RemoteOpenFileParent::OpenSendCloseDelete()). But it can be done earlier in parent whenever Webapps:Launch is notified. Later when child is looking for an entry, it is there ready for read.

This improves CPU utilization and makes content to be loaded faster. But there're things to consider beforehand:

- Now parent does not share JAR cache to child, need to work a way out to share the inflated data to child.
- What and how many files to inflate? App manifest has an attribute "launch_path" which is usually index.html. A roughly estimation on SMS app, it takes ~10ms to unzip index.html (24135 bytes). It's not worthy to save only 10ms with this much of work, but how do we know what else files to inflate?

	Ting-Yu Chou [:ting] (away) Reporter
	Comment 1 • 10 years ago

(In reply to Ting-Yu Chou [:ting] from comment #0)
> - What and how many files to inflate? App manifest has an attribute
> "launch_path" which is usually index.html. A roughly estimation on SMS app,
> it takes ~10ms to unzip index.html (24135 bytes). It's not worthy to save
> only 10ms with this much of work, but how do we know what else files to
> inflate?

No need to inflate more in parent if content process can receive the url when index.html finish unzip.

	Firefox Bug Husbandry Bot
	Comment 2 • 6 years ago

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.