Open
Bug 2043891
Opened 4 months ago
Updated 2 months ago
200ms spent in TC thread (compiling and eliminating phis) on https://retrotick.com/
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: mayankleoboy1, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug, )
Details
Go to https://retrotick.com/
Force-reload the page (CTRL+SHIFT+R) and watch the CPU use.
https://share.firefox.dev/4nYQ8Gc / https://share.firefox.dev/49v2Kiu / https://share.firefox.dev/4o1KOC3
Lots of time in compiling. Maybe something to improve?
| Reporter | ||
Updated•4 months ago
|
Summary: 170ms spent in TC thread (compiling?) on https://retrotick.com/ → 200ms spent in TC thread (compiling?) on https://retrotick.com/
| Reporter | ||
Updated•4 months ago
|
Summary: 200ms spent in TC thread (compiling?) on https://retrotick.com/ → 200ms spent in TC thread (compiling and eliminating phis) on https://retrotick.com/
Comment 1•4 months ago
|
||
The IonPerfSpewer => PCToLineNumber overhead is unfortunate but this shouldn't happen when the profiler is disabled though.
EliminatePhis being slower than register allocation is uncommon too. It's probably doing something quadratic.
Updated•4 months ago
|
Severity: -- → N/A
Priority: -- → P3
Comment 2•2 months ago
|
||
We've also seen potentially quadratic phi behaviour in bug 1942531, although it's not clear that the root cause there is the same as here.
You need to log in
before you can comment on or make changes to this bug.
Description
•