July 2, 2009 at 12:14Javascript performance? What about page redrawing performance?
- Transfer
Performance tests are now becoming more aggressive, while it seems that the emphasis is on artificial tests, which can show us the performance of only some browser components, in particular, the performance of JavaScript functions selected for these specific tests.
Surprisingly, so little attention is paid to other, more relevant aspects of the performance of modern pages, or not at all. For example, how fast do browsers with dynamically changing page styles (CSS) work?
At Velocity 2009, Lindsay Simon of Google spoke about this. And on the slides from the presentation there are a couple of interesting graphs .
It turned out that the Opera engine works very quickly with dynamically changing page content, and this is exactly what is used everywhere on the Internet. What if in the future browser performance is measured more comprehensively, unlike a simple JavaScript test?
Another nuance that I noted the other day is insufficient and highly specialized memory tests , which do not take into account that different browsers work with memory in different ways. For example, they ignore the shared memory of Chrome, and it does not seem that Opera’s advanced cache is taken into account.
In addition, Opera clears the cache of unused items every 10 minutes, but it is not visible that this would be reflected in the test report. We could clear the cache all the time, but then we would have to sacrifice performance, as Firefox seems to be doing.
In the context of complex JavaScript and memory testing , Jarakan seems to increase the performance of artificial JavaScript tests, but perhaps by using more memory.
Surprisingly, so little attention is paid to other, more relevant aspects of the performance of modern pages, or not at all. For example, how fast do browsers with dynamically changing page styles (CSS) work?
At Velocity 2009, Lindsay Simon of Google spoke about this. And on the slides from the presentation there are a couple of interesting graphs .
It turned out that the Opera engine works very quickly with dynamically changing page content, and this is exactly what is used everywhere on the Internet. What if in the future browser performance is measured more comprehensively, unlike a simple JavaScript test?
Another nuance that I noted the other day is insufficient and highly specialized memory tests , which do not take into account that different browsers work with memory in different ways. For example, they ignore the shared memory of Chrome, and it does not seem that Opera’s advanced cache is taken into account.
In addition, Opera clears the cache of unused items every 10 minutes, but it is not visible that this would be reflected in the test report. We could clear the cache all the time, but then we would have to sacrifice performance, as Firefox seems to be doing.
In the context of complex JavaScript and memory testing , Jarakan seems to increase the performance of artificial JavaScript tests, but perhaps by using more memory.