Closed
Bug 141518
Opened 23 years ago
Closed 17 years ago
page load regressed 26ms (1.2%), moz1.0 branch
Categories
(Core :: General, defect)
Core
General
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cathleennscp, Assigned: cathleennscp)
Details
(Keywords: perf, regression)
this check-in caused page load to increase from 2169ms to 2195ms on moz 1.0 branch http://bonsai.mozilla.org/cvsquery.cgi?module=MozillaTinderboxAll&branch=MOZILLA_1_0_0_BRANCH&date=explicit&mindate=1020197460&maxdate=1020202319 assign to av@netscape.com we need to address this immediately
fix for bug 106411 caused page-load regression. av is going to back out, then we'll let tinderbox run a few cycles to make sure tp gets back down.
My changes backed out. Let's see a couple of cycles if this helps.
Comment 3•23 years ago
|
||
I do not believe removing the code which shows something in the status bar can increase page loading. Let's see what we'll get.
Other machines which run this test don't show page load time increase. Could this be facedown problem?
Comment 5•23 years ago
|
||
yeah, the same trunk check in shows no increase of Tp: on btek http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey&maxdate=1020157204&le gend=0
face down reported no difference after av's backout. av, you're free to land back in later. I'm going to look for other possible cause. thanks.
Reassigning to the default owner of the selected component.
Assignee: av → waterson
here is the checkins one cycle before av's checkin. http://bonsai.mozilla.org/cvsquery.cgi?module=MozillaTinderboxAll&branch=MOZILLA_1_0_0_BRANCH&date=explicit&mindate=1020193200&maxdate=1020197459 we're going to try local backout on jkeiser's checkin on facedown tinderbox, while the tree is closed tomorrow morning, and verify.
Assignee: waterson → cathleen
Keywords: perf,
regression
Summary: page load regressed 26ms (1.2%) → page load regressed 26ms (1.2%), moz1.0 branch
Comment 9•17 years ago
|
||
This bug is obsolete.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•