Closed
Bug 1814808
Opened 3 years ago
Closed 3 years ago
Move chunk releasing out of the arena lock's critical section
Categories
(Core :: Memory Allocator, enhancement, P1)
Core
Memory Allocator
Tracking
()
RESOLVED
FIXED
112 Branch
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: pbone, Assigned: pbone)
References
(Blocks 1 open bug)
Details
(Keywords: perf:responsiveness, Whiteboard: [sp3])
Attachments
(1 file)
No description provided.
Assignee | ||
Comment 1•3 years ago
|
||
The system calls of releasing a chunk of memory can be costly and should be
done outside the arena lock's critical section so that other threads aren't
blocked waiting for the lock.
Assignee | ||
Comment 2•3 years ago
|
||
Performance results show some improvments on browser time tests on most pages, regressions on some pages, both mostly on Windows. No change on AWSY or Speedometer. There are some outlier results for speedometer on MacOS but they're too "lucky".
Pushed by pbone@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/850b602e5051
Move chunk releasing out of the arena lock's critical section r=glandium
Comment 4•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
Updated•3 years ago
|
Whiteboard: [sp3]
Updated•3 years ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SP3-248
You need to log in
before you can comment on or make changes to this bug.
Description
•