Closed Bug 379257 Opened 17 years ago Closed 17 years ago

Big jump in bl-bldxp01 perf numbers since 20070429 reboot

Categories

(Release Engineering :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

()

Details

(Keywords: regression)

Since the bug 379230 reboot, the numbers on bl-bldxp01 have taken an alarming leap - Tp from ~615 to pushing 680, Ts from 1900 to 2600 on the trunk, and on Mozilla1.8, Tp2 from 340 to 390, Ts from 1400 to 2000 (oddly, after an initial huge jump, Tp on 1.8 has settled down to only a worrisome jump).

Something on that box just ain't right.
Summary: Big jump in bl-bldxp01 perf numbers since 20040429 reboot → Big jump in bl-bldxp01 perf numbers since 20070429 reboot
In fact, if you look at 30 day charts, the numbers look quite a lot like the numbers from 20070401, which I got the impression from bug 376174 might have been the result of starting from RDP rather than VNC.
(In reply to comment #1)
> In fact, if you look at 30 day charts, the numbers look quite a lot like the
> numbers from 20070401, which I got the impression from bug 376174 might have
> been the result of starting from RDP rather than VNC.


Looks like it was started from VNC. If it was started from RDP the numbers would look ridiculously low because it takes almost no time to draw.
Keywords: regression
(In reply to comment #3)
> I don't know atm whether this jump is due to the box or a checkin

I do. During the period it was gone from 1.8, there were two checkins, one SeaMonkey-only, and one Camino-only.
nfi what happened between the trunk 2007/05/05 06:18 build and the 2007/05/05 06:47 build (other than "no checkins"), and little expectation that anyone will ever tell me, but, as of 6:47 am Saturday, WFM.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Assignee: build → nobody
QA Contact: mozpreed → build
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.