Hixie's Natural Log

2008-04-03 08:40 UTC The performance aspect of Acid3 on embedded devices

In my last post I discussed what "the animation has to be smooth" means for Web browsers on computers. Of course, embedded devices also have Web browsers, and Acid3 is as important for those as it is for a regular computer.

On embedded devices with smaller displays, the visual rendering may end up extending outside of the screen, but it should still look pixel-for-pixel identical to the reference rendering.

On devices with low power CPUs, the animation may end up being jerky, especially around test 26. This is because test 26 is significantly more CPU-intensive than the other tests.

On devices without a cache, the animation may be very jerky throughout. This is because without a cache, the test is affected by network conditions.

However, ideally, even embedded devices will have a cache and a CPU powerful enough to handle intense JavaScript. After all, they won't be able to handle big Web applications if they don't have the power to handle even a page like Acid3!

Pingbacks: 1