Nightly is 2.5x slower than Chrome on an online text comparator
Categories
(Core :: JavaScript Engine, task, P3)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 2 open bugs, )
Details
Attachments
(2 files)
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)
|
Reporter | |
Comment 1•1 year ago
|
||
|
|
Reporter | |
Comment 2•1 year ago
|
||
|
|
Reporter | |
Updated•1 year ago
|
|
||
Updated•1 year ago
|
|
|
Reporter | |
Comment 4•1 year ago
|
||
Reposting comment from :iain from https://bugzilla.mozilla.org/show_bug.cgi?id=1881910#c2 here:
(In reply to Iain Ireland [:iain] from comment #2)
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 fromcompute. Collapsing the subtree underneathcomputegives 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.
Description
•