-
Enhancement
-
Resolution: Unresolved
-
P3
-
beta
-
Fix Understood
-
generic
-
generic
A performace evalutaion of JAXB unmarshalling shows that obtaining/reseting
an instance of com.sun.xml.stream.ZephyrParserFactory.createXMLStreamReader(...)
is significate. It is 3/4 of execution time.
Module jaxb-performance in CVS repository :pserver:redcvs.red.iplanet.com:/sw/wpts
contains the apps and performace reporting tool (EJP) used for the evalutaion.
Sun stream code performace was compared to Xpp3 based MXparser.
I have compiled the Japex reports and relevant EJP performance reports in
the attached zip file. Files Xpp3PointDriver.html jaxbPointDriver_p1.html
contain the method level performace numbers for the P1 case. File
jaxbPointDriver_p1.html shows the time spend in each method of the
createXMLStreamReader call tree.
I commented out all the if (DEBUG_*) stmts in XMLEntityReaderImpl and
ran the performance tests above. In all cases execution time on
com.sun.xml.stream.ZephyrParserFactory.createXMLStreamReader(...) dropped
from 3 MS to 2 MS.
an instance of com.sun.xml.stream.ZephyrParserFactory.createXMLStreamReader(...)
is significate. It is 3/4 of execution time.
Module jaxb-performance in CVS repository :pserver:redcvs.red.iplanet.com:/sw/wpts
contains the apps and performace reporting tool (EJP) used for the evalutaion.
Sun stream code performace was compared to Xpp3 based MXparser.
I have compiled the Japex reports and relevant EJP performance reports in
the attached zip file. Files Xpp3PointDriver.html jaxbPointDriver_p1.html
contain the method level performace numbers for the P1 case. File
jaxbPointDriver_p1.html shows the time spend in each method of the
createXMLStreamReader call tree.
I commented out all the if (DEBUG_*) stmts in XMLEntityReaderImpl and
ran the performance tests above. In all cases execution time on
com.sun.xml.stream.ZephyrParserFactory.createXMLStreamReader(...) dropped
from 3 MS to 2 MS.