Xalan/Xerces Benchmarks

  File Size = 136.64Kb
					
  Schema is fairly simple (about 30 elems at 2nd level, each with 1 attribute and about 5 children elems, one of which has 0-30 of its own children elems)

PERFORMANCE
				             	  (seconds)
     		             	Load (DOM Parse)     Query - (XPath)   

Xalan2.0.1/Xerces1.4.4     -  	5.392	        	6.83
Xalan2.0.1/Xerces1.4.4     -  	4.243	        	6.8
Xalan2.0.1/Xerces1.4.4     -  	4.126	        	11.847

Xalan2.0.1/Xerces2.0Beta4  -  	4.734	        	6.5
Xalan2.0.1/Xerces2.0Beta4  -  	4.827	        	14.491 – bad test
Xalan2.0.1/Xerces2.0Beta4  -  	4.937	        	6.599

Xalan2.0.1/Crimson1.1.3    -	 	3.555			5.167
Xalan2.0.1/Crimson1.1.3    -	 	6.9			5.327

Xalan2.1.0/Xerces2.0Beta4  -	 	7.712			6.669
Xalan2.1.0/Xerces2.0Beta4  -	 	5.177			6.339		

Xalan2.2.0/Xerces2.0Beta4  -     	5.898			863.532
Xalan2.2.0/Xerces2.0Beta4  -	 	4.586			968.783

Xalan2.2.0/Crimson1.1.3    -	 	7.601			DNF
Xalan2.2.0/Crimson1.1.3    -	 	6.730			DNF

Xalan1.x/Xerces1.x	   -	 	7.071			7.992
Xalan1.x/Xerces1.x	   -	 	4.216			7.631

MEMORY

StringLib.xml file = 136.64Kb = .133Mb

Xerces1.4.4 = 1415Kb = 1.38Mb = 1037.59%
Xerces1.4.4 = 1449Kb = 1.41Mb = 1060.02%
Xerces1.4.4 = 1664Kb = 1.63Mb = 1225.56%

Xerces1.x = 2173.09Kb = 2.122Mb = 1595.49%
Xerces1.x = 1524.61Kb = 1.489Mb = 1119.46%

Xerces 2.0Beta4 = 2001.10Kb = 1.954Mb =  1467.69%

Crimson 1.1.3 = 1564.4Kb = 1.528Mb =  1148.87%
Crimson 1.1.3 = 1672.96Kb = 1.634Mb =  1228.38%

BUGS / NOTES

Xerces2.0Beta4 messes up parsing xml file, consistently mangles element value of one element!

Crimsons implementaion of the JAXP Interface seems different. Node.value is actual value of node (at least for attribute) unlike Xerces for which the value is node.child.value.  Would require some code rework.