greggman / greggman/webgpu-benchmark
Figure out why Firefox is so slow in this benchmark
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
It's possible there's an issue in the benchmark. It's also possible Firefox has a bug.
Here's the results on an M1 Mac connected to a 60hz monitor
chrome: 149.0.7827.157 (Official Build) (arm64)
safari tp: Release 246 (WebKit 22625.1.20.19.1)
firefox nightly: 154.0a1 (2026-06-23) (aarch64)
Looking above and seeing count/frame = 16 on all tests in firefox, it sounds like Firefox is throttling something. It might be that onSubmittedWorkDone is tied to vblank or requestAnimationFrame. It should arguably not be
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the benchmark on an M1 Mac with a 60Hz monitor using Firefox Nightly, Chrome, and Safari Technology Preview, then compare the count/frame results. Trace the benchmark's use of onSubmittedWorkDone and requestAnimationFrame to determine whether the throttling comes from the benchmark or Firefox. Done means identifying the cause and documenting or fixing the responsible behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100