Closed
Bug 397945
Opened 17 years ago
Closed 15 years ago
Reduce Tp overhead by 50% from Firefox 2
Categories
(Firefox :: General, defect, P2)
Firefox
General
Tracking
()
RESOLVED
INCOMPLETE
Firefox 3 beta3
People
(Reporter: mconnor, Assigned: mconnor)
References
Details
(Keywords: meta, perf)
We need some talos help to get this as a reliable metric, but we should be able to get this soonish. dtrace stats on chrome/chromeless would be awesome.
Flags: blocking-firefox3+
Updated•17 years ago
|
Updated•17 years ago
|
Assignee | ||
Updated•17 years ago
|
Target Milestone: Firefox 3 → Firefox 3 M11
Assignee | ||
Updated•17 years ago
|
Priority: -- → P5
Assignee | ||
Updated•17 years ago
|
Target Milestone: Firefox 3 Mx → Firefox 3 M11
Assignee | ||
Comment 2•16 years ago
|
||
deltas on 1.9 branch as of 3/3/2008: Vista: ~7-10% (numbers very noisy) XP: 14-15% (much less noisy) Linux: 3-5% (noisy) Mac: 15-19% (not so noisy) Not sure why Linux numbers are so much closer than Windows and Mac...
Comment 3•16 years ago
|
||
What were they in firefox 2? How close are we to this?
Comment 4•16 years ago
|
||
As of today, Mac is down to ~8-12% delta, but I don't know about FF2.
Assignee | ||
Comment 5•16 years ago
|
||
Stuart: we don't have reliable numbers (or, more accurately, any numbers) for Fx2. Pretty sure vlad was having problems with that even from the beginning (something like identical numbers with/without, which seems very odd, since we know there's _some_ cost to be had).
Assignee | ||
Comment 6•16 years ago
|
||
not going to block on this at this stage of the game, will try to take this the rest of the way during the next release.
Flags: blocking-firefox3+ → blocking-firefox3-
Assignee | ||
Comment 7•15 years ago
|
||
Not sure what the right resolution for tracking bugs that aren't quite relevant anymore... -> INCOMPLETE (We moved the needle, but we never reliable numbers on what we moved the needle _from_, so it's rather moot. Work continues.)
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•