2x slower than Chrome at setting HTMLInputElement.value on a text box
Categories
(Core :: DOM: Forms, defect, P3)
Tracking
()
People
(Reporter: mstange, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [sp3])
Attachments
(1 file)
(deleted),
text/html
|
Details |
On nearly all the TodoMVC tests, the value
setter of the text input shows up in the top 10 list of things that we are slower at than Chrome.
Fixing the performance difference should improve our numbers by 0.4% overall, which is equivalent to improving a single subtest by 8.5%. The test that benefits the most is TodoMVC-Svelte, because it does the least amount of other work.
Full Sp3 run profiles:
Firefox: https://share.firefox.dev/44DRpIw 1818 samples
Chrome: https://share.firefox.dev/44EgC5E 1078 samples
On the attached testcase, I get 820ms in Firefox and 320ms in Chrome.
Updated•1 year ago
|
Looks like that a lot of samples will be gone by the patch for bug 1845215.
Updated•1 year ago
|
Because of the fixes of the blockers, need new profile. (It seems that there are still bottlenecks in the editor and the selection.)
Reporter | ||
Comment 3•1 year ago
|
||
Updated profiles:
Firefox: https://share.firefox.dev/3YGv8aD 1775 samples
Chrome: https://share.firefox.dev/47D9gRz 1081 samples
Thank you. It seems that we don't have so many things to optimize existing leaf code anymore. It seems that we need design changes for putting off some unnecessary things.
Reporter | ||
Comment 5•1 year ago
|
||
Bug 1849286 has improved the time spent in the setter by 8%.
Before: https://share.firefox.dev/44pbDVj 1730 samples
After: https://share.firefox.dev/44qkc2d 1596 samples
Chrome: https://share.firefox.dev/3YVfzw3 1085 samples
Description
•