2.5x slower than Safari in Document.querySelector on TodoMVC-JavaScript-* subtests
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
People
(Reporter: mstange, Assigned: emilio)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sp3])
Attachments
(1 file, 1 obsolete file)
8.28 KB,
text/html
|
Details |
In the attached testcase, I get the following numbers:
Firefox Nightly: 480ms
Chrome Canary: 373ms
Safari Technology Preview: 190ms
Matching Safari's performance would improve our score by 1% on these three Speedometer3 subtests: TodoMVC-JavaScript-ES5, TodoMVC-JavaScript-ES6, TodoMVC-JavaScript-ES6-Webpack
Another issue in the benchmark (which is not reproduced by this testcase) is the fact that our selector parsing cache doesn't seem to persist across iframe reloads, whereas Safari's does.
Reporter | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Assignee | ||
Comment 3•2 years ago
|
||
It doesn't really need to.
Updated•2 years ago
|
Comment 4•2 years ago
|
||
Comment on attachment 9338489 [details]
Bug 1837673 - Make selector cache not tied to a document. r=#style,#layout
Revision D180591 was moved to bug 1837816. Setting attachment 9338489 [details] to obsolete.
Assignee | ||
Updated•2 years ago
|
Comment 5•2 years ago
|
||
The severity field is not set for this bug.
:jwatt, could you have a look please?
For more information, please visit BugBot documentation.
Reporter | ||
Comment 6•2 years ago
|
||
After bug 1839082 we now match or even exceed Safari's performance on this testcase. This is now fixed.
Updated•2 years ago
|
Comment 7•2 years ago
|
||
I've tested in MacOS 11: Nightly v118.0a1 and Beta v117.0b7 show relatively constant results of 400ms and above while Safari shows a relatively constant result of 400ms and below. Compared to the considerable difference originally reported, this is a huge improvement. Improvements are also seen in Windows 10, directly proportional to the ones on MacOS. An improvement in branch 116, then another considerable improvement in branch 117. This fix is confirmed.
Description
•