Firefox is 45x slower than Chrome at setAttribute on <input type="number">
Categories
(Core :: DOM: Forms, defect)
Tracking
()
People
(Reporter: mstange, Assigned: emilio)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [sp3])
Attachments
(8 files)
(deleted),
text/html
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/plain
|
Details | |
(deleted),
text/x-phabricator-request
|
Details |
On the attached testcase, I get 955ms in Firefox and 21ms in Chrome. https://share.firefox.dev/43eo7yv
Making Firefox as fast as Chrome on this testcase would improve our time on the "Perf-Dashboard" subtest of speedometer3 by 4.5%.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
A Nightly from 2020-01-14 actually performs better than Chromium in this case, very interesting
Nightly from 2020-01-14: 24ms
Current Chromium: 29ms
Nightly from 2020-01-15: 1178ms
3:21.82 INFO: Last good revision: 12d8255184b1015ff34f35c6fb040bbde6be2ed3 (2020-01-14)
3:21.82 INFO: First bad revision: c35bb210b8ae793c844bd94c1848d246bf601293 (2020-01-15)
3:21.82 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=12d8255184b1015ff34f35c6fb040bbde6be2ed3&tochange=c35bb210b8ae793c844bd94c1848d246bf601293
Comment 3•1 year ago
|
||
Nice find, I'm guessing bug 981248.
Assignee | ||
Comment 4•1 year ago
|
||
WIP - This is still not as fast as it should be (see FIXME).
Updated•1 year ago
|
Assignee | ||
Comment 5•1 year ago
|
||
Depends on D183254
Assignee | ||
Comment 6•1 year ago
|
||
Depends on D183281
Assignee | ||
Comment 7•1 year ago
|
||
It is always called from TextControlState, and always ends up in
TextControlState::ValueEquals, so we can avoid some indirection and just
use that.
Depends on D183282
Assignee | ||
Comment 8•1 year ago
|
||
This avoids a lot of useless time on things like GetValueAsDecimal(),
where we get the default value as a string, parse it as a number for
sanitization reasons, localize it to a string, just to parse it back to
a number.
Depends on D183283
Assignee | ||
Updated•1 year ago
|
Reporter | ||
Comment 10•1 year ago
|
||
Assignee | ||
Comment 11•1 year ago
|
||
Err sorry that ni? Was meant to be for me!
Comment 13•1 year ago
|
||
Comment 14•1 year ago
|
||
Comment 15•1 year ago
|
||
Assignee | ||
Comment 16•1 year ago
|
||
Intentionally not in the PGO list.
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Comment 17•1 year ago
|
||
Comment 18•1 year ago
|
||
Comment 19•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/e6231ae7b201
https://hg.mozilla.org/mozilla-central/rev/b48a8a347379
https://hg.mozilla.org/mozilla-central/rev/2a2ee1032045
Updated•1 year ago
|
Comment 20•1 year ago
|
||
Set release status flags based on info from the regressing bug 981248
Assignee | ||
Comment 21•1 year ago
|
||
Reopening for the last two patches.
Comment 22•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/f457492531e8
https://hg.mozilla.org/mozilla-central/rev/7799c0e4b59a
Comment 23•1 year ago
|
||
The patch landed in nightly and beta is affected.
:emilio, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox116
towontfix
.
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Comment 25•1 year ago
|
||
With the latest nightly, we are as fast as Chrome now.
Chrome: 21ms
Nightly: 22-23ms (28ms with profiler active: https://share.firefox.dev/3XMhqTr)
Comment 27•1 year ago
|
||
Comment 28•1 year ago
|
||
bugherder |
Description
•