There is a lot of buzz going on now about the new Google Chrome browser, and a lot of different testing of its performance against other browsers.
We take performance very seriously, thousands of ppl use TinyMCE every day, it is important that it works smooth on the browsers, not just loading performance, but also the performance of all the stuff that’s going on under the hood when you work with the editor.
So, the tests we have seen online so far have been very wide spread, showing insane performance improvements, but what are they testing? Is there any real-world implications of these performance tests?
TinyMCE uses DOM operations a lot, we have our own test bed, and these are the tests we are running.
- Serializer – This tests the cleanup functionality, a lot of DOM operations.
- Style parser/serializer – Tests a lot of string and array handling.
- URI – Tests a lot of regexp performance, converting URLs back and forth.
And these are the results.
The performance is measured in milliseconds, lower is of course better.
We could not install MSIE 8 beta on the same machine as MSIE 7, so no tests for that right now. The testing machine is a Windows Vista 64-bit, 4GB ram, 2.66gz Dual Core. Tests where performed with nothing other than the testing browser running.
Safari comes out on top of performance, with Firefox close behind, however we did not see any improvements when enabling the new JIT compiler in Firefox 3.1 Nightly build.
Results vary a bit up and down, but you can perform these tests yourself at this location.
These tests try a lot of different things at the same time, using the TinyMCE API, the performance improvements that the browser developers have been bragging about does not seem to be there, at least not in the areas interesting for most developers (DOM operations).