[meta] Improve speedometer 3 score
Categories
(Core :: Performance, task, P1)
Tracking
()
People
(Reporter: plawless, Unassigned)
References
(Depends on 100 open bugs)
Details
(Keywords: meta, perf)
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Reporter | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 1•1 year ago
|
||
S1 is "(Catastrophic) Blocks development/testing, may impact more than 25% of users, causes data loss, likely dot release driver, and no workaround available".
For meta bugs, there is no requirement to set severity.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 2•10 months ago
|
||
Perf key word?
Comment 3•10 months ago
|
||
(In reply to Worcester12345 from comment #2)
Perf key word?
Comment 4•9 months ago
|
||
Does this bug take the place of the "Matic's Performance Tracker" bug? (I can't find that one right now)
Does anyone pay attention to this bug?
reducing the flash of white on same-origin navigations
If this comment is not suitable to appear here, please tell me the right place
The V8 team made a faster HTML parser and it resulted in a 3.4% increase in Speedometer, WebKit also implemented it. Could this be applied to Firefox? From here https://v8.dev/blog/holiday-season-2023 and here is the other link https://github.com/WebKit/WebKit/pull/9926
Comment 7•3 months ago
|
||
See bug 1821615 - it may be worthwhile eventually, but at the moment the bottlenecks during innerHTML parsing are in code that would also be exercised by the fast path parser (element node creation etc).
Description
•