We estimate that 2 weeks should be plenty of time to get a good
baseline and allow people to start using tp5 as reference rather than
tp4.
We will bring this up to the developers' meeting and make sure that is
alright to shut tp4 on June 30th (except older release branches).
This adds ~15 mins for each tp run compared to just running tp4.
Let me know if you have any questions.
Regards,
Armen
-> bug 601798
This was brought up at yesterday's developer meeting and no one raised
any questions or concerns.
I will raise this up on next Tuesday meeting to make sure everyone is
aware.
If you have any comments about it or find a bug please let us know on
bug 661010.
cheers,
Armen
On Jun 16, 1:37 pm, armenzg <arme...@gmail.com> wrote:
> I forgot to post this on dev.planning as well.
I have a related question, actually. Tp5 doesn't seem to be in
compare-talos. Can we fix that before disabling Tp4 so that performance
comparisons can still be done?
> If you have any comments about it or find a bug please let us know on
> bug 661010.
Is that the right bug number? Seems unrelated to Tp4....
-Boris
Who are the owners of the following?
https://services.forerunnerdesigns.com/compare-talos/
http://perf.snarkfest.net/compare-talos/
Which one is the official one?
Right! bug 664831 that is.
>
> -Boris
Thanks Boris!
~Daniel
> _______________________________________________
> dev-tree-management mailing list
> dev-tree-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-tree-management
Awesome! Does tbpl also need updating to set the right URI? The one it
sends right now looks like this:
which excludes Tp5.
-Boris
https://bugzilla.mozilla.org/show_bug.cgi?id=666711
cheers,
Armen
Also, does Try Chooser (both the hook and the syntax builder) need updating?
-Boris
BTW when we disable tp4 I would like to remove it as it will return
empty comparison.
>
> Also, does Try Chooser (both the hook and the syntax builder) need
> updating?
The Try Syntax gets updated automatically.
The Try Chooser web page needs to be updated manually:
http://hg.mozilla.org/users/lsblakk_mozilla.com/trychooser/rev/639ee77ced36
>
> -Boris
Man this is finicky!
Thanks a lot Boris, doing things to the last details is very important.
cheers,
Armen
Huh. So it's just called "tp" in the try syntax now and that triggers
both tp4 and tp5 at the moment but will switch to just tp5? Or just
triggers tp5 already?
> Man this is finicky!
> Thanks a lot Boris, doing things to the last details is very important.
No problem. If I think of anything else, I'll bring it up. ;)
Are we getting all this down in a checklist for next time we roll out a
new test suite, by the way?
-Boris
>> Man this is finicky!
>> Thanks a lot Boris, doing things to the last details is very important.
>
> No problem. If I think of anything else, I'll bring it up. ;)
I am glad you do! :)
>
> Are we getting all this down in a checklist for next time we roll out a
> new test suite, by the way?
I added a note on the bug and added a checklist on the a-team's wiki page.
https://bugzilla.mozilla.org/show_bug.cgi?id=664831#c4
https://wiki.mozilla.org/Auto-tools/staging#Newer_suites
>
> -Boris
The tbpl and compare-talos issues were ironed out.
This is also to be announced on the platform meeting tomorrow.
For more details please read:
http://armenzg.blogspot.com/2011/06/disabling-tp4.html
cheers,
Armen
cheers,
Armen
Well, an additional interesting question is why Tp5 doesn't show the
regression....
-Boris
On another note, I can find a regression that tp5 found but not tp4:
Search for "Talos Regression :( Tp5 (Private Bytes) increase 3.74% on
MacOSX 10.6.2 Firefox"; is this right?
From looking at the email regression notifications I have seen that
every time a regression is found there is around a ~2% difference [1].
Considered that, the regression that roc is looking into is 2.68% for
tp4 and the tp5 difference could be around 0.68% or less (or even more
if my theory fails).
I am CCing other people that could answer this question.
Also note that these are two different sets of pages and perhaps the
newer set of pages can have pages that have intentionally made so they
are harder to run slow no matter what browser runs them. (NOTE:
Hypothesis of a non-expert in the field of browser performance).
For example: [1]
- 6.97%/5.97%
- 5.14%/3.8%
- 145%/131% (14 points difference but we are also talking about 3 digits)