Closed Bug 1837673 Opened 2 years ago Closed 2 years ago

2.5x slower than Safari in Document.querySelector on TodoMVC-JavaScript-* subtests

Categories

(Core :: CSS Parsing and Computation, defect)

defect

Tracking

()

VERIFIED FIXED
117 Branch
Tracking Status
firefox-esr102 --- wontfix
firefox-esr115 --- wontfix
firefox115 --- wontfix
firefox116 --- wontfix
firefox117 --- verified
firefox118 --- verified

People

(Reporter: mstange, Assigned: emilio)

References

(Blocks 1 open bug)

Details

(Whiteboard: [sp3])

Attachments

(1 file, 1 obsolete file)

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.

Flags: needinfo?(emilio)
Depends on: 1837734
Depends on: 1837762
Depends on: 1837816

It doesn't really need to.

Assignee: nobody → emilio
Status: NEW → ASSIGNED
Depends on: 1837818

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.

Attachment #9338489 - Attachment is obsolete: true
Depends on: 1839082
Flags: needinfo?(emilio)

The severity field is not set for this bug.
:jwatt, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jwatt)

After bug 1839082 we now match or even exceed Safari's performance on this testcase. This is now fixed.

Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(jwatt)
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch

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.

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: