1868744 - If JS engine triggered a GC slice, don't trigger another too soon from CCGCScheduler

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, enhancement, P3)

Description

[Olli Pettay [:smaug][[e-mail]]]

This is not for performance as such, but to reduce noise.
And tryserver results seem to hint that this is useful for that
https://treeherder.mozilla.org/perfherder/comparesubtest?originalProject=try&newProject=try&newRevision=6c22f5bc6a4f04158150383f010e066ec3b28200&originalSignature=4586009&newSignature=4586009&framework=13&application=firefox&originalRevision=01c54f106b2576c3faf7ae69aa98a230db627493&page=1

If more GC slices are needed, then JS engine will of course trigger them normally. It is just that CCGCScheduler won't be so eager to do it too.

Comment 1

[Olli Pettay [:smaug][[e-mail]]]

Attachment: Bug 1868744 - If JS engine triggered a GC slice, don't trigger another too soon from CCGCScheduler, r=jonco

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/6767f1605049
If JS engine triggered a GC slice, don't trigger another too soon from CCGCScheduler, r=jonco

Comment 3

[Iulian Moraru]

https://hg.mozilla.org/mozilla-central/rev/6767f1605049