IntroductionI would like to show some performance benchmarks for Apache CXF on SPARC/Solaris 11 Platform. CXF was deployed in OSGi Karaf container and uses Jetty as Web Server.
JMS communication was done using Apache ActiveMQ broker, database access was based on EclipseLink JPA with Apache Aries managed transactions and Oracle DB server.
A lot of thanks for colleges Marian Kueffner for composing and integration of benchmark results and Christian Schneider for supporting me with the tests.
- Measure maximum CXF service invocation throughput on a particular hardware configuration: SPARC/Solaris 11
- Identify bottlenecks, areas of tuning and enhancements
SPARC / Solaris 11 SUN-T4-2-FAMILY-0 30351017 SPARC T4-2 512GB – 8 GbE Ports – 4 FC Ports – 4 10GbE *604532* Ports
- 2x SPARC T4 8-Core 2,85 Ghz. processor
- 512GB RAM (32x 16GB DDR3 DIMM MODULES)
- 6x 600GB SAS2 10k HDD
- 2x Qlogic FC 8Gbps HBA PCIe
- 2x 10 GbE SFP+ HBA PCIe
- 1x 1 GbE Quad Gigabit Ethernet HBA PCIe
Deployment: Karaf OSGi (Equinox based) container
- Java: 6 (build 1.6.0_26-b3)
- CXF: 2.6.0
- Karaf: 2.2.6
- Jetty: 7.5.4
- Aries: 0.3.1
- ActiveMQ: 5.6.0
- EclipseLink: 2.3.0
Benchmarks were measured for three main scenario:
- (A) JAX-WS based Web Services (SOAP over http)
- (B) Messaging over JMS/ActiveMQ (SOAP over JMS)
- (C) Database access via Service (EclipseLink, container managed transaction, Oracle)
Scenario A: small messages with DOM model; HTTP
Scenario A: small messages with stream model; HTTP
Scenario A: medium messages with DOM model; HTTP
Scenario A: large messages with DOM model; HTTP
Special Scenario: maximal service load
In this scenario service was loaded using 4 clients: three SoapUI and one CXF. Clients were activated sequentially with 1 minute interval. You can see how service load changing when the next client becomes active.
Scenario B: small messages with DOM model; JMS
Scenario B: medium messages with DOM model; JMS
Scenario B: large messages with DOM model; JMS
Scenario C: Inserts in Oracle DB using EclipseLink JPA and Aries transactions
Scenario C: Selects from Oracle DB using EclipseLink JPA and Aries transactions
Generally CXF shows high performance in described scenarios on Sun Solaris Platform.
I have some remarks regarding the benchmark results:
- Single thread shows pretty low performance, but system is highly scalable. Perhaps Solaris should be additionally tuned for single thread.
- Service (provider) is very scalable. As you can see in the Test Case 5, adding more consumers just increases the service throughput. I reach more than 10K messages per second, but it still was not the top.
- JMS scenario with ActiveMQ shows relative low performance with default configuration. The numbers are much higher if persistence is deactivated or at least immediate synchronization is switched off.
- Stream oriented message processing increases throughput on 25-30% even for small messages.