Hi, We're working on a rewrite of the localization infrastructure in Gecko and tpaint is the main perf test that we're affecting.
My team has put a lot of work over last weeks to better understand tpaint tests. The test at the moment is both noisy, and has a steady regression with each run which makes it hard to feel confident about it and also makes it impossible to just increase the number of runs in order to increase significance and reliability of the result. Basically, tpaint does 20 runs and currently each run is slower than the previous one. I believe it may affect your experience of using the test. What's more, the test doesn't only test opening a new window, but it also loads a document into it (via data: protocol) and measures first paint after the document is loaded. We found out that the regression is visible in tpaint (window.open + document load), but not in MozAfterPaint of the browser chrome UI, so your patch may have an impact on the tpaint *without* affecting the new window performance. I'm documenting the findings in https://bugzilla.mozilla.org/show_bug.cgi?id=1295292 Seems like :jimm can't commit to it right now, so if anyone else knows how to fix it and has cycles, it might help us make better decisions about our code. zb. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
