> Do we realistically care about keeping this working? With perfherder > graphs, we now have a way of visualizing/tracking relative performance (http://wrla.ch/blog/2015/02/measuring-e10s-vs-non-e10s-performance-with-perfherder/), > though I'm not sure if that's really telling us anything we don't > already know.
We're rolling e10s out this year so e10s and non-e10s talos numbers are important. Long term e10s numbers are all we will care about since non-e10s will be unsupported. > If we *do* decide we care about these results, I think we should (1) > enable e10s runs on integration branches and (2) commit to backing out > commits that break talos on e10s (i.e. unhide them) We do and I agree, they should be visible and running as often as regular talos runs trigger. e10s perf regressions on Nightly should be treated the same way other talos regressions would. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
