I consider myself enlightened after reading the article. By applying the canvas performance optimization methods in the article, Construct 2 runtime could benefit from a significant increase in performance.Mipey2011-11-02 15:29:14
I read that article, but most of the tips apply to software renderers. We're gunning for hardware accelerated implementations all round. Things like not rendering at floating point co-ordinates only make a difference for software renderers - on hardware accelerated canvases there should be no measurable difference.
From my own tests I would actually say even though Chrome now has hardware acceleration, IE9 is still top. Its canvas is still about 25% faster and is even better quality too - you get nice antialiasing on object edges, which Chrome and Firefox don't appear to do.
Although we don't support it yet you can get much better performance from using WebGL, so IE could still end up slowest.