Hi Greg and others, I was just about to raise the issue of performance regression from this change. If we are aiming this at the 49 release, I would like for us to improve the situation described in bug 1259923, a 15% performance regression across all Talos tests covering Windows platforms, which Joel brought to my attention yesterday. I don't think we can accept that if it means a large noticeable slowdown in performance for Windows users in the release population. (Even though we really, really want to improve the toolchain and build time for developers and our own infrastructure.)
Can we put some engineering resources into investigating the test results and mitigating the perf regression? 15% worse across all Windows tests should probably block the release. We don't have hard and fast criteria for what would be an acceptable perf hit. I think the platform (and probably product team) should discuss that. Thanks, Liz On Tue, May 31, 2016 at 4:22 PM, Gregory Szorc <g...@mozilla.com> wrote: > Heads up: we'll soon be dropping support for building mozilla-central with > VS2013. Bug 1186064 tracks and the patch has already received r+. > > I'm going to wait a few days before landing because this could be > disruptive and I want to at least give a heads up before I create a fire. > Please install VS2015 in the next 48 hours to avoid a surprise the next > time you pull. > > (We've previously recommended everyone install VS2015, so this > announcement should come as no surprise.) > > _______________________________________________ > firefox-dev mailing list > firefox-...@mozilla.org > https://mail.mozilla.org/listinfo/firefox-dev > > -- ---- Liz Henry (:lizzard) Firefox Release Manager lhe...@mozilla.com _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
