Open
Bug 421524
Opened 16 years ago
Updated 2 years ago
25ms (2%) Tdhtml blip on qm-pxp-fast01
Categories
(Core :: General, defect)
Tracking
()
NEW
People
(Reporter: stevee, Unassigned)
References
Details
(Keywords: perf)
Attachments
(1 file)
39.06 KB,
image/png
|
Details |
It looks like one checkin gave us a 25ms Tdhtml win, and then another checkin cancelled this gain out. Maybe it was something to do with the testbox or something, but I'm filing anyway since I went and found ranges and we might want a 2% win if we can get it. WINNT 5.1 mini talos trunk fast qm-pxp-fast01 build start 2008/03/05 12:08:47 tdhtml: 1290.59 build start 2008/03/05 13:59:38 tdhtml: 1265.53 Checkins to module PhoenixTinderbox between 2008-03-05 12:08 and 2008-03-05 13:59 : http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=PhoenixTinderbox&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-03-05+12%3A08&maxdate=2008-03-05+13%3A59&cvsroot=%2Fcvsroot build start 2008/03/05 22:03:54 tdhtml: 1267.50 build start 2008/03/05 23:33:56 tdhtml: 1298.18 Checkins to module PhoenixTinderbox between 2008-03-05 22:03 and 2008-03-05 23:33 : http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=PhoenixTinderbox&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2008-03-05+22%3A03&maxdate=2008-03-05+23%3A33&cvsroot=%2Fcvsroot
Flags: blocking-firefox3?
Reporter | ||
Comment 1•16 years ago
|
||
http://graphs.mozilla.org/graph.html#spst=range&spstart=0&spend=1204778167&bpst=cursor&bpstart=0&bpend=1204778167&m1tid=148125&m1bl=0&m1avg=0
Updated•16 years ago
|
Flags: blocking-firefox3?
Product: Firefox → Core
QA Contact: general → general
Reporter | ||
Updated•16 years ago
|
Flags: blocking1.9?
Comment 2•16 years ago
|
||
Looks like bug 415854 might be the culprit. When we have time we should investigate if that is intentional.
Updated•16 years ago
|
Flags: tracking1.9+
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•