Open Bug 1501825 Opened 3 years ago Updated 3 years ago

Understand relationship between process count and tps Talos score

Categories

(Core :: DOM: Content Processes, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: mconley, Assigned: mconley)

References

Details

In bug 1470280, we bumped the default max content process count to 8. We're likely to continue increasing the max content process count even more over time as we tear away at Fission.

After that landed, we noticed a mixture of tps regressions and improvements.

Copied here, but originally from bug 1497785 comment 3:

== Change summary for alert #16593 (as of Tue, 09 Oct 2018 18:07:51 GMT) ==

Regressions:

 19%  tps windows7-32 pgo e10s stylo     10.71 -> 12.77
 11%  tps windows7-32 opt e10s stylo     12.13 -> 13.49
  7%  tps linux64 opt e10s stylo         10.80 -> 11.61
  7%  tps linux64-qr opt e10s stylo      9.18 -> 9.80

Improvements:

 13%  tps windows10-64 pgo e10s stylo        11.72 -> 10.17
  9%  tps windows10-64 opt e10s stylo        12.44 -> 11.30
  7%  tps windows10-64-qr opt e10s stylo     9.58 -> 8.88

For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=16593


I'd like to understand the relationship between content process count and the tps score. Why are some platforms improving and some regressing?
Assignee: nobody → mconley
Depends on: 1502088
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.