Chrome is faster on WebGL Fishbowl demo

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
8 years ago
7 years ago

People

(Reporter: jrmuizel, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

()

Attachments

(1 attachment)

At 2000 fish I get about 23fps in FF but get 60FPS in Chrome.

81% of the time is spent under EnterMethodJIT

It looks a there's a bunch of heap churn from things like JSObect::allocSlots()
also 3.6% of the time is is in js::mjit::stubs::UncachedCallHelper()

Comment 1

8 years ago
Can you post the profiles?
(In reply to comment #1)
> Can you post the profiles?

Sure (http://people.mozilla.com/~jmuizelaar/fishbowl/Instruments2.trace.gz) but it should be easy enough to just profile.
Posted image GCTimer output
The GC pauses are only 4msec :)

Comment 4

8 years ago
Yeah probably L2 cache misses on allocation and maybe the frequent mallocs.
Sure the object growth seems to be a problem. Maybe bug 547327 would help?

I never get 60FPS with Chrome. It's only 22 for the release and 40 for the canary version. FF nightly is also 22 FPS for me.
I get 60 fps with 2000 fish on OS X, with/without IonMonkey. Please reopen if you still see this.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.