Canvas vs SVG performance on iPad
techblog.floorplanner.com
Canvas vs SVG performance on iPad
1–10 of 15 posts
Re: Canvas vs SVG performance on iPad
#2Painting a single rectangle against a timer resolution of 1 millisecond (which the browser won't even do) pretty much tells you nothing.
Re: Canvas vs SVG performance on iPad
#3I did not know that Android does not support SVG. What's the reason?
Re: Canvas vs SVG performance on iPad
#4Somehow I doubt that SVG is being completely repainted every time its coordinates change. And since the repaints are asynchronous, I don't see how you could time them from within JavaScript.
Re: Canvas vs SVG performance on iPad
#5I don't think these test results are anywhere close to accurate. Why is the iPhone 4, which has better specs than the iPad 1, 3x slower in the Canvas test? What OS was used on each device? How many test runs were done, and what was the variation like in each?
Re: Canvas vs SVG performance on iPad
#6I believe this test proves little useful across different browsers on different OS/hardware because setInterval and setTimeout cannot fire faster than 8-10ms on most browsers and every browser handles a "1ms" request differently.
http://dbaron.org/log/20100309-faster-timeouts
However the postMessage trick is near realtime:
Re: Canvas vs SVG performance on iPad
#7I believe this test proves little useful across different browsers on different OS/hardware because setInterval and setTimeout cannot fire faster than 8-10ms on most browsers and every browser handles a "1ms" request differently. http://dbaron.org/log/20100309-faster-timeouts However the postMessage trick is near realtime: http://dbaron.org/mozilla/zero-timeout
The point of a settimeout or setinterval is that it will always process in the next run loop. I don't see how postMessage actually provides anything over calling a function directly.
Re: Canvas vs SVG performance on iPad
#8Painting a single rectangle against a timer resolution of 1 millisecond (which the browser won't even do) pretty much tells you nothing.
Yes, exactly. I have a little web game that renders in SVG, and it puts up ~8000 shapes on the screen, updates at about 5hz on most desktop machines. This is ok, since it's basically a panning map that doesn't get panned much. If I switched to Canvas, it'd run quite quickly, but I'd lose all the wins from using the DOM.
Re: Canvas vs SVG performance on iPad
#9I believe this test proves little useful across different browsers on different OS/hardware because setInterval and setTimeout cannot fire faster than 8-10ms on most browsers and every browser handles a "1ms" request differently. http://dbaron.org/log/20100309-faster-timeouts However the postMessage trick is near realtime: http://dbaron.org/mozilla/zero-timeout
The point of a settimeout or setinterval is that it will always process in the next run loop. I don't see how postMessage actually provides anything over calling a function directly.
When I update to setZeroTimeout in those canvas vs svg demos, the drawing is so fast there is horizontal tearing and the frame rates are in the thousands.
Which means the FPS with setInterval is actually measuring how long it takes setInterval to fire, not how long it's taking to draw under the different methods.
Re: Canvas vs SVG performance on iPad
#10Somehow I doubt that SVG is being completely repainted every time its coordinates change. And since the repaints are asynchronous, I don't see how you could time them from within JavaScript.
I guess that not repainting everything can be an advantage of SVG. Can you think of a way to time repaints better?