Closed
Bug 479102
Opened 16 years ago
Closed 14 years ago
TM: Improve performance of code we don't trace well
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: gal, Assigned: gal)
References
Details
(Keywords: meta)
We currently incur very substantial perf regressions on code we don't trace well. That shouldn't be the case. Examples are v8 benchmarks and https://bugzilla.mozilla.org/show_bug.cgi?id=458016.
Assignee | ||
Updated•16 years ago
|
Flags: blocking1.9.1?
Priority: -- → P1
Target Milestone: --- → mozilla1.9.1b3
Updated•16 years ago
|
Flags: blocking1.9.1? → blocking1.9.1+
Target Milestone: mozilla1.9.1b3 → ---
Assignee | ||
Updated•16 years ago
|
Summary: TM: Improve blacklist → TM: Improve performance of code we don't trace well
Comment 1•16 years ago
|
||
this morphed into a meta bug, and we don't block on those.
Flags: blocking1.9.1+ → blocking1.9.1-
Keywords: meta
Assignee | ||
Updated•16 years ago
|
Priority: P1 → --
Comment 2•15 years ago
|
||
I found that tracer working even when jit is disabled.... is it possible to disable tracer at all? (I want to use trunk engine but without perf regessions in JS because of Tracer....)
Comment 3•14 years ago
|
||
Jägermonkey solved this issue.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•