Closed Bug 1874040 Opened 5 months ago Closed 4 months ago

Slow performance on https://github.com/public-apis/public-apis compared to Chrome

Categories

(Core :: DOM: Core & HTML, defect)

Firefox 121
All
Unspecified
defect

Tracking

()

RESOLVED FIXED
Performance Impact low

People

(Reporter: ksenia, Assigned: emilio)

References

(Blocks 1 open bug)

Details

Attachments

(2 files, 2 obsolete files)

​​### Basic information
This was initially reported in https://github.com/webcompat/web-bugs/issues/131302 where a user is experiencing slow page and content load

Steps to Reproduce:

  1. Sign in on GitHub
  2. Visit https://github.com/public-apis/public-apis

Expected Results:
Page and content loads fast

Actual Results:
Page and content load takes a lot of time


Performance recording (profile)

Profile URL: https://share.firefox.dev/3SeCe4V (recorded in Firefox Nightly 123.0a1 (2024-01-02))

System configuration:

OS version: Windows 10, but can be reproduced on other platforms as well

Emilio has indicated this might be improved by: https://bugzilla.mozilla.org/show_bug.cgi?id=1866161

The Performance Impact Calculator has determined this bug's performance impact to be low. If you'd like to request re-triage, you can reset the Performance Impact flag to "?" or needinfo the triage sheriff.

Platforms: Windows
Impact on site: Causes noticeable jank
Websites affected: Rare
[x] Able to reproduce locally

Performance Impact: --- → low
Component: Performance → DOM: Core & HTML

The page loads fast to me in Nightly.
Bug 1866161 landed awhile ago, but I think there was some other fix which landed recently.

I can reproduce on Nightly.

Attached file Attempt at a test-case. (obsolete) —
Attachment #9379220 - Attachment mime type: text/plain → text/html

Comment on attachment 9379220 [details]
Attempt at a test-case.

Meh, that doesn't work. In any case it seems to be this code.

Attachment #9379220 - Attachment is obsolete: true
Depends on: 1879579
Regressions: 1879579
No longer regressions: 1879579

Setting to S3 because of "performance impact: low". Feel free to upgrade it if this is more important.

Severity: -- → S3
Flags: needinfo?(emilio)

Make sure to do no work on insertions if the dir=auto element has
already the right strong directionality, but record that the node might
be the one impacting the dir=auto resolution.

Also get some node flags back.

To be landed after merge of course.

Assignee: nobody → emilio
Status: NEW → ASSIGNED

This is probably because I've been awake for too long at this point
while traveling back from CSSWG meetings, but these make my head
spin.

Let's avoid the double-negatives. I think it's easier to reason
about.

Depends on D202071

Uh, latest version has some orange on try which I need to fix up.

Flags: needinfo?(emilio)
Depends on: 1881011
Attachment #9380652 - Attachment is obsolete: true

This test caught a subtle bug in one of the versions of my previous
patch, but it caught it by chance.

The reason it got caught is because the reftest harness uses a mutation
observer, and thus disables the textContent optimization that reuses the
text node.

WPT didn't catch this, so move the test there, and add tests for the
characterData mutation and removal-and-append explicitly, to not depend
on textContent optimizations.

Flags: needinfo?(emilio)
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4ce4c83e0d85
Move 1103348-1.html to WPT, and expand it. r=smaug
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/44697 for changes under testing/web-platform/tests
Keywords: leave-open
Blocks: 1881225
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ddd358fef977
Simplify dir=auto implementation. r=smaug
Upstream PR merged by moz-wptsync-bot
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: