5 ms·
I have to hand it to IE these days, their performance boasts aren't just lip service. They are definitely outpacing Chrome and FF on canvas performance. Chrome
by simonsarris 12y ago
I have to hand it to IE these days, their performance boasts aren't just lip service. They are definitely outpacing Chrome and FF on canvas performance.
Chrome used to dither between best and second best in performance in the last 4 years, but for some time now IE10 + 11 have been the fastest browsers at rendering 2D Canvas paths/primitives/images by a huge margin.
I develop a canvas-based library and have a series of tests[1] that also serve as a (somewhat practical than usual) benchmark for how browsers compare when using canvas. Here's how long it takes to complete the tests on the big three:
FF nightly: 17.713 seconds
Chrome dev: 13.123 seconds
IE 11: 7.83 seconds
Chrome had an edge when I started out with canvas stuff, now IE is almost twice as fast as Chrome.
[1] you can run the tests yourself here: http://gojs.net/latest/tests/index.html http://gojs.net/latest/tests/index.html but remember that its only meaningful if you compare results on the same machine.
- cromwellian 12y agoIt's easy to do this when you only need to address a single platform. Most of that overhead is probably bound to graphics layer overhead. Microsoft tightly couples to DirectX. Chrome has to sit on top of SKIA to support Win/Linux/OSX/Android. I bet Safari Canvas performance is also high, since they can directly bind to OSX.
- masklinn 12y ago> I bet Safari Canvas performance is also high, since they can directly bind to OSX. On my machine (old MBP, 10.9.5) Firefox 33: 35.2s Safari 7.1: 18.57s Chrome 34[0]: 28.6s [0] yes I know it's not up to date
- ossreality 12y ago[0]: it's not even close
- sitharus 12y agoon my 2012 rMBP running 10.10: Firefox 33: 33.255 Safari 8.0: 16.454 Chrome 38: 22.048 I should install Windows 10 tech preview underbootcamp and see how that goes.
- cromwellian 12y agoI get 12.287 secs under Safari 8/Yosemite on a Mac Pro (2014) 8-core. 15.9 secs on Chrome Canary (40.x) 20.3 secs on FF30. My guess is IE11 1) has lower OS/driver overhead and 2) accelerates more Canvas ops and does less software rendering than other platforms.
- pjmlp 12y agoThey just need to make use of respective hardware accelerated APIs in each targeted platform.
- munificent 12y agoThere are a lot of dragons hiding in that "just".
- vanderZwan 12y agoI recall being blown away by IE10 svg performance - is it still the fastest there too? EDIT: Surprisingly, svg benchmarks are hard to find. All I get is Canvas benchmarks.
- ygra 12y agoNot really a benchmark, but anecdata, but for us at work (we're doing graph drawing, layouting, and editing using SVG for graphics in the browser) IE is consistently fastest, Chrome comes second and Firefox usually last. SVG doesn't seem to be much of a priority for them, sadly.
- vanderZwan 12y agoIt really feels like a vicious cycle at times, doesn't it? Nobody uses it because it's slow, it's slow because nobody uses it.
- acdha 12y agoNow I'm curious which video driver features they depend on for full optimizations. Running on a current MacBook Air inside VMWare Fusion, IE11 and Chrome have very similar performance: IE11 in a VM: 24.874 Chrome in a VM: 24.137 As an aside, I'm impressed that the overhead of running in VMWare was that fast. It's within a factor of two of the best native performance: FF 33: 24.577 Chrome: 16.908 Safari: 13.004
- yfefyf 12y agoI swithed from chrome to IE a few weeks before. Because IE is faster. And my computer is quieter using IE.