Closed Bug 588057 Opened 14 years ago Closed 14 years ago

Huge regression on 3d-raytrace in today's Trunk Nightly

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
major

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- final+

People

(Reporter: teoli, Unassigned)

References

Details

(Keywords: perf, regression)

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:2.0b4pre) Gecko/20100817 Minefield/4.0b4pre
Build Identifier: 

Yesterday and all the day before (since landing of fatvals on the Trunk, who already regressed it a little bit) I got 58-60 ms for 3d-raytrace.

In today's nightly I get 124 ms for it.

bitops-bitwise-and regressed from 1.8 to 5.4 ms too.

But all others sunspider tests didn't changed.


Reproducible: Always
Status: UNCONFIRMED → NEW
Ever confirmed: true
Blocks: 552828
blocking2.0: --- → ?
Keywords: perf, regression
I am looking for some Mozilla Talos links that show this regression. I don't
see it on tinderboxpushlog or dev.tree.management.
Are you seeing this regression in the JS shell or in the browser?
(In reply to comment #4)
> Are you seeing this regression in the JS shell or in the browser?

I'm seeing the same regression in the browser (currently 32bit nightly on 64bit windows 7).
(In reply to comment #4)
> Are you seeing this regression in the JS shell or in the browser?

I'm also seeing the regression in the browser (32-bit nightly on 32-bit OS X 10.5)
Hardware: x86 → All
Version: unspecified → Trunk
Attached file V8 test results
Wow. If you take a look at V8 it's even more dramatic.

Drew a comparison table of the two hourly builds before/after bug 552828's landing.
Check out all the other results apart from RayTrace...
Bug 588201 restores the performance. It has landed and the 3D ray trace numbers are back to normal levels.

Bug 588201 increases the amount of memory used for the JIT cache. A deeper problem was found in the process. From bug 588201:

"Setting such a small value also constitutes a stress test of the tracer, which
apparently exposed the assertion in bug 588128."
Fixed by bug 588201
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
blocking2.0: ? → final+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: