I would guess blindly that not many people react or read this
newsgroup. There are > 50 messages a day for talos "improvements" and
"regressions". Most of them are probably noise, not real improvements or
regressions. There's no clear indication of what one should do about it,
outside of hunting down the bugs responsible (which to echo mbrubeck
seems to be the only person really looking at). Talos noise is
considerable:
https://wiki.mozilla.org/Auto-tools/Projects/Signal_From_Noise ,
https://wiki.mozilla.org/images/c/c0/Larres-thesis.pdf . Graphserver is
not wonderful at helping me figure out what has regressed or even what
tests are what.
I'm not trying to be a complainer or doom-sayer here. I am trying to
draw attention to the fact that A. Firefox performance testing is hard,
complex, and has lots of moving pieces; and B. consequently, since we
don't have anyone who's job it is to analyze all of this madness, we
mostly just ignore it (except for mbrubeck). We (=jmaher, Jonathan
Eads, Christina Choi, and myself) have been working on making this
better, end to end, but it is a huge job, much much bigger than the
single quarter for which the project was originally planned.
In my opinion, to make people care you need a system that is easy (maybe
even fun) to use, and you need to have a person who's job it is to sort
through this (huge amount of) data. Kudos to mbrubeck for stepping up
to the plate. He does a huge amount of work. But I'd love to see
someone really mining this data and figuring out what should be done.
> _______________________________________________
> dev-tree-management mailing list
>
dev-tree-...@lists.mozilla.org
>
https://lists.mozilla.org/listinfo/dev-tree-management