Closed Bug 512250 Opened 15 years ago Closed 15 years ago

Chrome is way faster at bubble mark then firefox

Categories

(Core :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 497788

People

(Reporter: jrmuizel, Unassigned)

Details

Chrome runs at about 200 fps. Safari at about 98 fps, and us at 86fps. Not sure why yet.
Chrome doesn't self-limit timeouts to 10ms minimum delay. Other browsers do. /be
We spend about 20% in js: getting and setting. About 40% in painting and the rest scattered about.
(In reply to comment #1) > Chrome doesn't self-limit timeouts to 10ms minimum delay. Other browsers do. > > /be Yes, that looks like the reason.
However, if you set the number of balls to 128 and adjust the setInterval time to 10ms Chrome gets 72fps and we get 25fps. So there's still some work we can do here.
Yes, there's more to do, but this is already tracked at bug 497788. /be
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.