On 12-08-29 8:10 PM, Justin Lebar wrote:
After getting an e-mail every single time m-c was merged for a day or two, I filtered the e-mails and completely forgot about them. I imagine most other people did the same. If we fix bug 752002, we'd also need to change the e-mails so as to get around everyone's existing filters.
And hope that they do not add new filters. ;-)
More on topic: I think the essential problem is, you can spend a week chasing down a perf regression when there's a good chance it's not your fault (and also a good chance it's not a regression). So people are making a reasonable trade-off here when they ignore these problems.
I don't necessarily agree. The common practice as far as I can tell is for people to not investigate, *assuming* the above. I don't believe we have data to support any of these propositions on an average case.
This is the essential problem that the Signal from Noise project is tackling. But it's a medium-term play at best, since they're rewriting large pieces of infrastructure. So the question is: Are we willing to sit back and wait for SfN, or do we need improvements Right Now? It's my feeling that incremental improvements are often more beneficial than the "stop fixing all but critical bugs in existing code, focus on v2 code" approach that we seem to be taking with SfN, but I understand that there are trade-offs here.
I agree. I don't think that the SfN project will be a magic bullet here.
Anyway there are simple things we could do to improve the current situation without taking too much of the focus away from SfN, such as unbreaking compare-talos (e.g. [1], but also in general applying real statistics so it's simple to find true regressions and rule out false ones). It's just a question of priorities.
Absolutely. Ehsan _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
