Regression: Tp4 increase 6.99% on Linux Firefox
Previous results: 511.495 from build 20091116061047 of revision f360de4b8b08 at 2009-11-16 06:51:00 on talos-rev2-linux07 run # 0
New results: 547.273 from build 20091116083213 of revision ebc28a0d4b96 at 2009-11-16 09:11:00 on talos-rev2-linux07 run # 0
Suspected checkin range: from revision f360de4b8b08 to revision ebc28a0d4b96
Intereting. See, Honza's patch should NOT have had any Tp effect. I
was a bit surprised that it correlated with one on both m-c and 1.9.2,
but did those just land at the same time?
What were the timeframes for the three regressions (m-c, t-m, 1.9.2)?
-Boris
Regression: Tp4 increase 7.04% on Linux Firefox
Previous results: 511.495 from build 20091116061047 of revision f360de4b8b08 at 2009-11-16 06:51:00 on talos-rev2-linux07 run # 0
New results: 547.495 from build 20091116061047 of revision f360de4b8b08 at 2009-11-17 08:46:00 on talos-rev2-linux07 run # 1
Suspected checkin range: from revision f360de4b8b08 to revision f360de4b8b08
That's an empty range.
-Boris
Looking at the graph, there was a big drop in Tp4 on Linux around Nov 1
and that now it's gone back to the level we had before Nov 1.
I don't see any reports in this newsgroup of the 6% Tp4 drop around Nov 1.
I also don't know why there was a drop, nor the rise now...
-Boris
I asked Honza to backout his patch from mozilla-central, to see if the Tp4 number goes down again. The graph on 1.9.2 also seems to show a regression, and I'll back it out from 1.9.2 as well in case it really proves to be a regression.
--
Ehsan
<http://ehsanakhgari.org/>
On Mon, Nov 16, 2009 at 4:41 PM, Ehsan Akhgari <ehsan....@gmail.com> wrote:
On Mon, Nov 16, 2009 at 4:36 PM, Nobody <nob...@cruncher.build.mozilla.org> wrote:
Regression: Tp4 increase 6.99% on Linux Firefox
Previous results: 511.495 from build 20091116061047 of revision f360de4b8b08 at 2009-11-16 06:51:00 on talos-rev2-linux07 run # 0
New results: 547.273 from build 20091116083213 of revision ebc28a0d4b96 at 2009-11-16 09:11:00 on talos-rev2-linux07 run # 0
Suspected checkin range: from revision f360de4b8b08 to revision ebc28a0d4b96