1 SoftwareGroup WebSphere 
2014. 
© Copyright IBM Corporation 2014 
Performance comparison 
according to size of WSDL including XSD file 
IBM SoftwareGroup WebSphere CTP 
JungWoon Lee, juwlee@kr.ibm.com
1. Conditions 
 Conditions for performance test 
- Goal : To verify performance degradation of JAX-WS initialization(JAXB context creation, 
marshalling and unmarshalling) according to size of WSDL including XSD file 
- WAS : IBM WebSphere Application Server v8.5.5 
- HW : Lenovo T420 : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, Memory 8GB 
- Load Test Tool : open-source Apache Jmeter 
- Test Architecture : 
JAX-WS 
WebService Client 
JAX-WS 
WebService Provider 
- Application : simple JAX-WS webservice application with varargs parameter 
- The way to increase size of wsdl including xsd file 
> Once create webservice application with sample VO file which should add 50 line to wsdl 
2 SoftwareGroup WebSphere 
and xsd 
-> Then, replicate the VO file after changing name and then refer them with @XmlSeeAlso 
annotation 
WebSphere 
WebSphere 
JMeter
 Conditions for performance test 
- Use simple application without business logic to analyze the spent time for application 
initialization 
- Using @XmlSeeAlso annotation, refer VO classes and increase size of WSDL and XSD 
3 SoftwareGroup WebSphere 
1. Conditions 
JAX-WS 
WebService Client 
JAX-WS 
WebService Provider
4 SoftwareGroup WebSphere 
2. The Result 
 The Result of performance test
5 SoftwareGroup WebSphere 
2. The Result 
 The Result of performance test 
☞ Summary 
-> The more size of wsdl including xsd file, the more time spent at the initialization. 
After that, it shows similar results regardless of numbers of VO files because of using cached 
JAXB context.
EEnndd ooff TThhee DDooccuummeenntt.. 
6 SoftwareGroup WebSphere
EEnndd ooff TThhee DDooccuummeenntt.. 
6 SoftwareGroup WebSphere

Varargs perf ibmwas_comp_v02_e

  • 1.
    1 SoftwareGroup WebSphere 2014. © Copyright IBM Corporation 2014 Performance comparison according to size of WSDL including XSD file IBM SoftwareGroup WebSphere CTP JungWoon Lee, juwlee@kr.ibm.com
  • 2.
    1. Conditions Conditions for performance test - Goal : To verify performance degradation of JAX-WS initialization(JAXB context creation, marshalling and unmarshalling) according to size of WSDL including XSD file - WAS : IBM WebSphere Application Server v8.5.5 - HW : Lenovo T420 : Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, Memory 8GB - Load Test Tool : open-source Apache Jmeter - Test Architecture : JAX-WS WebService Client JAX-WS WebService Provider - Application : simple JAX-WS webservice application with varargs parameter - The way to increase size of wsdl including xsd file > Once create webservice application with sample VO file which should add 50 line to wsdl 2 SoftwareGroup WebSphere and xsd -> Then, replicate the VO file after changing name and then refer them with @XmlSeeAlso annotation WebSphere WebSphere JMeter
  • 3.
     Conditions forperformance test - Use simple application without business logic to analyze the spent time for application initialization - Using @XmlSeeAlso annotation, refer VO classes and increase size of WSDL and XSD 3 SoftwareGroup WebSphere 1. Conditions JAX-WS WebService Client JAX-WS WebService Provider
  • 4.
    4 SoftwareGroup WebSphere 2. The Result  The Result of performance test
  • 5.
    5 SoftwareGroup WebSphere 2. The Result  The Result of performance test ☞ Summary -> The more size of wsdl including xsd file, the more time spent at the initialization. After that, it shows similar results regardless of numbers of VO files because of using cached JAXB context.
  • 6.
    EEnndd ooff TThheeDDooccuummeenntt.. 6 SoftwareGroup WebSphere
  • 7.
    EEnndd ooff TThheeDDooccuummeenntt.. 6 SoftwareGroup WebSphere