Closed Bug 608490 Opened 14 years ago Closed 14 years ago

Profiler slower than straight -j on the second testcase in bug 604905

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 608480
Tracking Flags:
Tracking Status
blocking2.0 --- final+

People

(Reporter: bzbarsky, Assigned: billm)

References

(Blocks 1 open bug,
URL
)

Details

(Keywords: regression, Whiteboard: [jsperf]) 

See url field for testcase.

The times for 1000x1000 I see are:

-m -j -p: 370ms
-m -j   : 335ms
-m      : 440ms
   -j   : 127ms

If I only run the 1000x1000 test, -m -j ends up the same speed as -j, while -m -j -p is still slower (167ms vs 133ms).

I can't get you more data than that yet, because debug shell with -j fatally asserts.  Filed bug 608489 on that.
Whiteboard: [jsperf]
Assignee: general → wmccloskey
Blocks: 580468
blocking2.0: --- → ?
Keywords: regression
As far as I can tell, the patch in bug 608480 fixes this.
Depends on: 608480
blocking2.0: ? → final+
Judging from comment 1 and bug 608480 comment 5, this is a dup of bug 608480.  Please reopen if I'm mistaken.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.