- Introduction
- Performance Summary for RPC-Style Web Service Exchange
- Performance Summary for Document-literal Web Service with Low Payload
- Performance Summary for Document-literal Web Service with Medium Payload
- Performance Summary for Document-Literal Web Service with High Payload
- Analysis
- Implementation Issues with Axis Document-Literal Messaging
- Conclusion
Performance Summary for Document-Literal Web Service with High Payload
Payload size: High (200KB)
Ramp up: 25 users per minute
Iteration pacing: 120 seconds
Total test duration: 27 minutes
Figure 4 shows response time versus number of virtual users for this test.
Figure 4 Performance summary for document-literal web service with high payload.
The following table shows the results of each measurement.
Measurement |
Result |
Number of users at 29.5% CPU utilization |
500 |
Total transactions failed |
0 |
Average response time |
0.752 seconds |
We see encouraging numbers again. With a heavy payload of 200KB per transaction, we could ramp up the simultaneous users to 500 before hitting 30% CPU utilization. The average roundtrip overhead was noted around 700 millisecondsstill less than a second, under a very heavy load of simultaneous users handling a large payload. Again, the most impressive number was that of no failures in any transactions.