About performances

Performance test (seconds) Init JS
Time spent to make document in ready state
HP DC5700 2xCPU Windows XP 2002 Pack 3
CPU bound 50% by all
Distant Server. Windows 2003 IIS 6

Browsers IE(8.0),FF(3.0),CH(1.0),SA(3.2),OP(9.64)

Persons Load small Load medium Load large
Chrome .500 .300 1.600 14.000
IE8 2.400 1.400 NA(a) NA(a)
FF3 1.700 0.800 5.900 69.000
Safari 1.700 1.300 3.400 51.000
Opera 1.000 .500 14.800 520.000

Tests

  1. Persons: see
  2. Load Small: Instance with 100 elements with two attributes.
  3. Load Medium: Same as above but with 1000 elements.
  4. Load Large: same as above with about 6000 elements.

An XSLTForms document is an XML document

  1. Step 1: the document is transformed to an HTML document
  2. Step 2: onload a JavaScript initialize underlying structures of the HTML document


(a) IE prompts repeativily for stopping the js script (I did not found to how to configure IE in order to avoid warning loops)! Depending on Browser configuration parameters the same problem can occurs with others (Messages such: a script is slowing your computer, do you want to stop script execution for this page). This may be a problem with end users, they can imagine a bug or intrusion. Finally: setting a key named MaxscriptStatements in styles directory of IE width a high value (DWORD) solves the problem.

Chrome seems to have have a very good JavaScript Engine !
Xslt CPU (Step 1) cost is peanuts regarding js init() (Step 2) with all browsers

The XSLTForms js comes from AjaxForms project, it contains its own XPath processor and XML parser. So it doesnt depend on browser implementation, but it runs very slowly regarding native use of functions supported by recent browsers.

FF3 (FF2), Opera (9.5), Safari (3.0) Support DOM 3 standard interfaces (as far as bugs rise)

IE (6,7,8) Supports DOM 3 according to msxml version, with non standard access functions and methods for XPath. But one can use standard DOM interface for event management.

For instance: IE does not support XPath navigation on HTML DOM Document. Mapping of XPath evaluate on MsXml is not very easy.
In NET3.0 then NET3.5 MS made a lot of sophisticated extensions such Xlinq (not XLink)