Closed
Bug 1951042
Opened 1 year ago
Closed 1 year ago
Testcase from bug 1945382 gets superlinearly slower compared to Chrome - 44x for N=100k, 98xfor N=200k, 195x for N=300K
Categories
(Core :: CSS Parsing and Computation, enhancement)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
1.60 KB,
text/html
|
Details |
- Open the attached testcase (Original testcase from bug 1945382)
- Enter 100k and press apply
- Wait for the stylesshets to be generated and applied. We are faster than Chrome here \o/
- Now without reloading the page or anything, enter 1 and press Apply.
- Wait for the stylesshet to be applied - > This steps is very slow.
N=100K (44x slower)
- Nightly: https://share.firefox.dev/3XnnC54 (7s)
- Chrome: https://share.firefox.dev/3CXFcG8 (160ms)
N=200K (98x slower)
- Nightly: https://share.firefox.dev/3DnrBb3 (41s)
- Chrome:https://share.firefox.dev/4hVZcrz (420ms)
N=300K (195x slower)
- Nightly: https://share.firefox.dev/3CZEDM1 (103s)
- Chrome: https://share.firefox.dev/3QBOWbY (530ms)
| Reporter | ||
Updated•1 year ago
|
Flags: needinfo?(emilio)
Comment 1•1 year ago
|
||
Yeah so the test-case is removing from the front which is not particularly amazing. We could perform some sort of batching, but not clear that'd be faster for the common cases either tbh. So probably wontfix unless we see this show up in real websites.
Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(emilio)
Resolution: --- → WONTFIX
| Reporter | ||
Comment 2•1 year ago
|
||
Thanks for checking Emilio.
You need to log in
before you can comment on or make changes to this bug.
Description
•