727383 - performance in javascript-command&conquer is magnitudes worse than in chrome

Status: RESOLVED DUPLICATE of bug 718481

(Core :: Graphics: Canvas2D, defect)

Description

[Dave]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a2) Gecko/20120214 Firefox/12.0a2
Build ID: 20120214042008

Steps to reproduce:

open
http://www.adityaravishankar.com/projects/games/command-and-conquer/
and observe performance


Actual results:

it was really slow


Expected results:

it should have been fluid (as in chrome e.g.)

Comment 1

[David Teller [:Yoric] - still alive but not very active]

Just to be sure: have you determined for sure that it is JS speed and not, say, display speed? If so, we can triage this bug to the JS team.

Comment 2

[Thomas Ahlblom]

Reproduced (very slow and jerky):
Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1
Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0
Mozilla/5.0 (X11; Linux x86_64; rv:12.0a2) Gecko/20120214 Firefox/12.0a2
Mozilla/5.0 (X11; Linux x86_64; rv:13.0a1) Gecko/20120215 Firefox/13.0a1

WFM:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.77 Safari/535.7
Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.10.229 Version/11.61

/usr/bin/X consumes 75% CPU while running Firefox, and Firefox itself 25% CPU.

Comment 3

[Thomas Ahlblom]

(In reply to David Rajchenbach Teller [:Yoric] from comment #1)
> Just to be sure: have you determined for sure that it is JS speed and not,
> say, display speed? If so, we can triage this bug to the JS team.

I interpret "javascript-command&conquer" as the bug is about command&conquer written in JavaScript, not necessarily that the bug is in JavaScript itself. The high CPU usage by X in Linux indicates that it's not primarily a JavaScript problem.

Can someone running Windows find out which process makes the computer lag?

Comment 4

[Thomas Ahlblom]

/usr/bin/X uses 3 % CPU with Chromium (vs 75% with Linux).

Comment 5

[Thomas Ahlblom]

(In reply to Thomas Ahlblom from comment #4)
> /usr/bin/X uses 3 % CPU with Chromium (vs 75% with Linux).

Eeeeh!

…(vs 75 % with Firefox)

Comment 6

[Dave]

> Can someone running Windows find out which process makes the computer lag?
>
I'm running Windows, on my 4-core i7 firefox.exe uses a constant of 25% overall
(or mashes one core to put it in other words).

Is there a way to inspect the usage more fine-grained?

Comment 7

[Dave]

> Just to be sure: have you determined for sure that it is JS speed and not,
> say, display speed? If so, we can triage this bug to the JS team.
>
nope - what I wanted to say is that the lag occurs when playing around with "js-C&C". I don't really have a clue which part of FF is responsible for that mess :-) might be JS, might be UI, might be anything...

How can one trace where that cycles go?

Comment 8

[Dave]

y u no reply?

Comment 9

[Josh Matthews [:jdm]]

I'm pretty sure bug 718481 has more analysis in it and is therefore more actionable.