Buffer allocator medium allocations store metadata as part of the allocation
Categories
(Core :: JavaScript: GC, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox140 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
(Blocks 1 open bug)
Details
(Keywords: perf-alert)
Attachments
(6 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Following on from bug 1960811 we can do a similar thing for medium sized buffers and store their metadata packed in the chunk header rather than at the start of the allocation.
Assignee | ||
Comment 1•29 days ago
|
||
These were removed previously in bug 1960811.
Assignee | ||
Comment 2•29 days ago
|
||
Standardizes on one term for the pointer to allocated memory return to the client.
Assignee | ||
Comment 3•29 days ago
|
||
Header doesn't make sense now these are not always stored at the start of
allocation. The structures themselves are named like FooBuffer, so use 'buffer'
for these pointers everywhere.
Assignee | ||
Comment 4•29 days ago
|
||
Assignee | ||
Comment 5•29 days ago
|
||
Assignee | ||
Comment 6•29 days ago
|
||
Now we can remove the buffer header entirely. This is mostly a simplificiation.
Comment 8•25 days ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/30fa80635f50
https://hg.mozilla.org/mozilla-central/rev/e66e33001e50
https://hg.mozilla.org/mozilla-central/rev/2f8a3558e2c8
https://hg.mozilla.org/mozilla-central/rev/55fb84dea632
https://hg.mozilla.org/mozilla-central/rev/717f6c86d1d4
https://hg.mozilla.org/mozilla-central/rev/4eac62f1e440
Comment 9•23 days ago
|
||
7.5% improvement on Ares6-Basic_Average
Comment 10•8 days ago
|
||
(In reply to Serban Stanca [:SerbanS] from comment #8)
https://hg.mozilla.org/mozilla-central/rev/30fa80635f50
https://hg.mozilla.org/mozilla-central/rev/e66e33001e50
https://hg.mozilla.org/mozilla-central/rev/2f8a3558e2c8
https://hg.mozilla.org/mozilla-central/rev/55fb84dea632
https://hg.mozilla.org/mozilla-central/rev/717f6c86d1d4
https://hg.mozilla.org/mozilla-central/rev/4eac62f1e440
Perfherder has detected a talos performance change from push 4eac62f1e4409647b70eeb13aaab64bbfd6b2d61.
If you have any questions, please reach out to a performance sheriff. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.
Improvements:
Ratio | Test | Platform | Options | Absolute values (old vs new) |
---|---|---|---|---|
6% | pdfpaint bug1826783.pdf | macosx1470-64-shippable | e10s fission stylo webrender-sw | 550.57 -> 516.65 |
Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.
If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a performance sheriff to do that for you.
You can run all of these tests on try with ./mach try perf --alert 45069
The following documentation link provides more information about this command.
Description
•