Closed Bug 1371242 Opened 3 years ago Closed 3 years ago
Investigate if CC slices could use idle periods more likely
Attachment #8875674 - Attachment is obsolete: true
remote: View your change here: remote: https://hg.mozilla.org/try/rev/791551c65ebb4cf43dffa614e5bef2754294abf9 remote: remote: Follow the progress of your build on Treeherder: remote: https://treeherder.mozilla.org/#/jobs?repo=try&revision=791551c65ebb4cf43dffa614e5bef2754294abf9 remote: remote: It looks like this try push has talos jobs. Compare performance against a baseline revision: remote: https://treeherder.mozilla.org/perf.html#/comparechooser?newProject=try&newRevision=791551c65ebb4cf43dffa614e5bef2754294abf9 remote: recorded changegroup in replication log in 0.118s
Attachment #8876374 - Attachment is obsolete: true
Comment on attachment 8881575 [details] [diff] [review] idle_ccgc_tweak_5.diff Tweaking CC budgets a bit, and also try to run CC based on timer a bit less often. nsCycleCollector_collectSlice also starts to use the second param again in case we don't have a known long slice. Element::ClearContentUnbinder(); call is there to try to avoid long first CC slice.
Attachment #8881575 - Flags: review?(continuation)
Attachment #8881575 - Flags: review?(continuation) → review+
Summary: Investigate if CC/GC slices could use idle periods more likely → Investigate if CC slices could use idle periods more likely
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/c69701b058e8 try to run CC slices more likely during idle periods, r=mccr8
You need to log in before you can comment on or make changes to this bug.