Comment 0 for bug 768462

Right now (r5), it takes ~1070ms to render 60 frames on my Samsung Captivate, varying pretty widely above and below. In a perfect world it would consistently take 1000ms. I'd like to get as close to that as possible (or at the very least, be consistent...)

This bug is going to stay open for a looong time, but it needs to be something I'm watching out for throughout development.