Open
Bug 812201
Opened 12 years ago
Updated 2 years ago
Scirra RenderPerf3 slower than chrome
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
NEW
People
(Reporter: vlad, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [games:p?][js:t])
The benchmark at http://www.scirra.com/labs/renderperf3/ gets around 142k in Chrome, vs. 66k in Firefox on my box with a 560 Ti. On my work desktop with a faster CPU with a Quadro 2000, they both get around 33k. No idea why Chrome gets such a big win on a faster GPU, but we should figure it out.
Reporter | ||
Updated•12 years ago
|
Whiteboard: [games:p2]
Comment 1•12 years ago
|
||
Profile:
http://people.mozilla.com/~bgirard/cleopatra/#report=9ea4d029e60cbef674355a567cc83bfc71a91b05
View:
http://tinyurl.com/cf443cr
We spend about 71% of our time in JS. This benchmark would also improve slightly (~5% I'd guess) from using double buffering.
My guess is this benchmark needs some JS tuning.
Reporter | ||
Comment 2•12 years ago
|
||
Yep, looks like it. Curious -- I wonder why that's different on my Quadro 2000 box? I guess the 3D cost ends up overriding the JS cost? Moving this to JS. Unfortunately the code is obfuscated, we can probably reach out and get unobfuscated one.
Assignee: nobody → general
Component: Canvas: WebGL → JavaScript Engine
Hardware: x86_64 → x86
Updated•12 years ago
|
Whiteboard: [games:p2] → [games:p2][js:t]
Updated•11 years ago
|
Blocks: gecko-games
Assignee | ||
Updated•10 years ago
|
Assignee: general → nobody
Whiteboard: [games:p2][js:t] → [games:p?][js:t]
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•