Open
Bug 1954006
Opened 2 months ago
Updated 1 month ago
Testcase generating N Wekref objects is 4x slowr and uses 4x more RAM.
Categories
(Core :: JavaScript Engine, task, P3)
Core
JavaScript Engine
Tracking
()
NEW
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
851 bytes,
text/html
|
Details |
Open attached testcase
N=5000000
Firefox: https://share.firefox.dev/41RHA9y (12s, 1.2GB)
Chrome: https://share.firefox.dev/3RfqDAV (3.5s, 300mb)
Testcase is extremely artificial. No ides if performance of Weakrefs is important.
|
||
Comment 1•2 months ago
|
||
27% of time spent in JS::Zone::traceKeptObjects. We could implement this using a generation count rather than an explicit set which is what I think JSC does. I'm not sure why the memory use is so much higher.
|
Reporter | |
Comment 2•2 months ago
|
||
Profile with JS and Native memory tracking if it helps: https://share.firefox.dev/3XT4Z9o
|
||
Updated•1 month ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•