Closed
Bug 664655
Opened 14 years ago
Closed 13 years ago
Chrome is faster on WebGL Fishbowl demo
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jrmuizel, Unassigned)
References
()
Details
Attachments
(1 file)
5.61 KB,
image/png
|
Details |
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•14 years ago
|
||
Can you post the profiles?
Reporter | ||
Comment 2•14 years ago
|
||
(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•14 years ago
|
||
The GC pauses are only 4msec :)
Comment 4•14 years ago
|
||
Yeah probably L2 cache misses on allocation and maybe the frequent mallocs.
Comment 5•14 years ago
|
||
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•13 years ago
|
||
I get 60 fps with 2000 fish on OS X, with/without IonMonkey. Please reopen if you still see this.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•