664655 - Chrome is faster on WebGL Fishbowl demo

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[Jeff Muizelaar [:jrmuizel]]

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

[Andreas Gal :gal]

Can you post the profiles?

Comment 2

[Jeff Muizelaar [:jrmuizel]]

(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.

Comment 3

[Gregor Wagner [:gwagner]]

Attachment: GCTimer output

The GC pauses are only 4msec :)

Comment 4

[Andreas Gal :gal]

Yeah probably L2 cache misses on allocation and maybe the frequent mallocs.

Comment 5

[Gregor Wagner [:gwagner]]

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.

Comment 6

[Jan de Mooij [:jandem]]

I get 60 fps with 2000 fish on OS X, with/without IonMonkey. Please reopen if you still see this.