Closed Bug 1817640 Opened 1 year ago Closed 1 year ago

Investigate how use of effectiveMaxDirty() would affect performance and AWSY

Categories

(Core :: Memory Allocator, task)

Product:
Core
Component:
Memory Allocator
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
112 Branch
Tracking Flags:
Tracking Status
firefox112 --- fixed

People

(Reporter: smaug, Assigned: smaug)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

Bug 1817640 - extract calculation of max dirty value to a helper method EffectiveMaxDirty(), r=glandium,pbone
48 bytes, text/x-phabricator-request
Details | Review
Attachment #9318618 - Attachment description: WIP: Bug 1817640 - extract calculation of max dirty value to a helper method EffectiveMaxDirty(), r=glandium,pbone → Bug 1817640 - extract calculation of max dirty value to a helper method EffectiveMaxDirty(), r=glandium,pbone
Assignee: nobody → smaug
Status: NEW → ASSIGNED
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/06ec7576d29d
extract calculation of max dirty value to a helper method EffectiveMaxDirty(), r=pbone

https://hg.mozilla.org/mozilla-central/rev/06ec7576d29d

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox112: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
Blocks: 1811541
Blocks: 1811784
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: