Zetaoffice demos take 30s to compile without lazy tiering, lazy tiering is 2s
Categories
(Core :: JavaScript: WebAssembly, enhancement, P3)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
|
45.20 KB,
text/plain
|
Details |
Writer:
Without Lazy tiering: https://share.firefox.dev/4aYI2Ho (28s)
With lazy tiering: https://share.firefox.dev/3CNKHHe (9s till the browser is usable. 2s in taskcontroller threads)
Chart:
Without lazy tiering: https://share.firefox.dev/3QgikEC (34s)
With lazy tiering: https://share.firefox.dev/4hBwtIG (8s till the browser is usable. 800ms in taskcontroller threads)
|
Reporter | |
Comment 1•1 year ago
|
||
|
||
Comment 2•1 year ago
|
||
It looks like they're shipping an enormous amount of wasm bytecode (at least 150MiB). We're shipping lazy tiering for all content soon (bug 1957504) and that will help here. To get any more improvement we would need to have lazy baseline compilation.
I think with how big the wasm code is here, 2 seconds isn't that bad. I'll leave this open as something we could investigate if we do lazy baseline compilation.
|
|
Reporter | |
Updated•1 year ago
|
Description
•