Oh man. Keeps getting wierder.
Yeah it looks like interpreting the wildly different results is going to make optimisations tricky. I'm anticipating similar issues now that I'm developing for several different platforms....or at least trying to
The coarse culling does reduce the amount document writes (can also reduce the need for repaints), but adds a bit more logic overhead AND more importantly, adds a lot of animated objects as culled objects are being faded out and then faded back in when they reappear.
I guess my next step is to create a semi-automated test that would try differentiate between write, gpu and cpu speeds.
Excuse my ignorance here
Do you have any idea what sort of ballpark performance we should expect from html5? How much CPU & GPU access does it have compared to other programs?