Open Bug 1811666 Opened 1 year ago Updated 1 year ago

JS demo (https://www.fxhash.xyz/generative/slug/littlecube-maps:-tropical-oasis-islands) is slower on Nightly compared to Chrome (and appears to spend time in non-JIT code)

Categories

(Core :: JavaScript Engine, task, P3)

task

Tracking

()

People

(Reporter: mayankleoboy1, Unassigned)

References

(Blocks 1 open bug)

Details

Go to https://www.fxhash.xyz/generative/slug/littlecube-maps:-tropical-oasis-islands
Click on "Open"

Nightly: https://share.firefox.dev/3QWH0Bt

Compared to Chrome, there are two slowdowns:

  1. In the 941ms jank near the beginning. Additionally, Nightly spends a lot of time in non-JIT code
  2. The micro janks that appear in the rest of the profile (indicated by the red jank bars)
Summary: JS demo (https://www.fxhash.xyz/generative/slug/littlecube-maps:-tropical-oasis-islands) is slower on Nightly compared to Chrome → JS demo (https://www.fxhash.xyz/generative/slug/littlecube-maps:-tropical-oasis-islands) is slower on Nightly compared to Chrome (and appears to spend time in non-JIT code)

The small main thread janks are structured clone reading. I want to try something.

Flags: needinfo?(jdemooij)
Depends on: 1812055
Flags: needinfo?(jdemooij)
Severity: -- → S3
Priority: -- → P3

Pofile with latest Nightly: https://share.firefox.dev/3XHyqcr

You need to log in before you can comment on or make changes to this bug.