Canvas performance on Mac with quartz backend for azure

UNCONFIRMED
Unassigned

Status

()

Core
Canvas: 2D
UNCONFIRMED
6 years ago
6 years ago

People

(Reporter: beingalink, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0a1) Gecko/20120129 Firefox/12.0a1
Build ID: 20120129031114

Steps to reproduce:

Run Canvas performance test on mac nightly 12.0a1 (2012-01-29): http://www.kevs3d.co.uk/dev/asteroidsbench/

Hardware acceleration is enabled in preferences. about:support says ...

  Graphics

        Vendor ID
        0x10de

        Device ID
        0x 863

        WebGL Renderer
        NVIDIA Corporation -- NVIDIA GeForce 9400M OpenGL Engine -- 2.1 NVIDIA-7.12.9

        GPU Accelerated Windows
        1/1 OpenGL

        AzureBackend
        quartz



Actual results:

Safari's score is considerately higher:
Benchmark Score: 2215
Average FPS: 47

vs. Nightly:
Benchmark Score: 899
Average FPS: 19



Expected results:

I'd expected them to be about equally fast.
I would be curious to see this comparison again on 10.6 where safari doesn't use the lion undocumented API.
(Reporter)

Comment 2

6 years ago
Sadly I don't have 10.6 installed for a comparison. I just tried the same benchmark using Google Chrome 16.0.912.77:

Benchmark Score: 991
Average FPS: 21

From that perspective Nightly's performance isn't even so bad. Though I don't know what graphics backend Chrome uses on the mac.
Thanks, we're already working on some patches to close that gap. We're hoping to land them in Firefox 13 if all goes well.

Comment 4

6 years ago
I have 10.6 on my laptop still here is what I got with Safari 5.1.4:

Benchmark Score: 1088
Average FPS: 23

FF Aurora (12):

Benchmark Score: 1337
Average FPS: 28

Benchmark #5 (spinning ship with green lasers) was very slow ~11fps pushing the average down I think for FF. The other tests were all noticeably faster in FF then Safari.
You need to log in before you can comment on or make changes to this bug.