Closed
Bug 1881910
Opened 2 years ago
Closed 2 years ago
Nightly is 2.5x slower than Chrome on an online text comparator
Categories
(Core :: JavaScript Engine, task)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 1881911
People
(Reporter: mayankleoboy1, Unassigned)
References
()
Details
Go to https://www.textcompare.org/
From the attached text files, select the "original" and the "modified" files
Click on compare. Make sure that the type of comparison is for Plaintext.
Chrome: https://share.firefox.dev/4bSQ44H (6s)
Nightly: https://share.firefox.dev/3IcghNL (14s)
Updated•2 years ago
|
| Reporter | ||
Updated•2 years ago
|
No longer blocks: sm-codepen-slower
Comment 2•2 years ago
|
||
Glancing at the profile, V8 is spending 93% of the time in compute, while we're only spending 32%. However, all the other hot functions are being called directly from compute. Collapsing the subtree underneath compute gives 95% for us. I think this implies that V8 is inlining more aggressively than we are, in which case maybe they can do a better job of optimizing the code post-inlining.
You need to log in
before you can comment on or make changes to this bug.
Description
•