Closed Bug 479102 Opened 15 years ago Closed 14 years ago

TM: Improve performance of code we don't trace well

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
normal

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.
Flags: blocking1.9.1?
Priority: -- → P1
Target Milestone: --- → mozilla1.9.1b3
Flags: blocking1.9.1? → blocking1.9.1+
Target Milestone: mozilla1.9.1b3 → ---
Summary: TM: Improve blacklist → TM: Improve performance of code we don't trace well
Depends on: 479109
Depends on: 479110
this morphed into a meta bug, and we don't block on those.
Flags: blocking1.9.1+ → blocking1.9.1-
Keywords: meta
Priority: P1 → --
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....)
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.