Project

General

Profile

Actions

Load Test on Prototype

The main purpose of this test is to examine the performance of the messaging system against the earlier defined expectation.

The test platform is:
  • Single core 1.6 GHz processor
  • 1 GB RAM
  • 60 GB 5400 RPM disk

Test against modules

Obtain the connection factory through JNDI.

Time taken to produce x number of message:
Test 100 Messages (seconds) 500 Messages (seconds)
1 9.265 51.703
2 9.938 48.765
3 10.062 52.032
4 10.078 48.265
5 9.625 52.094
6 9 50.484
7 9.391 49.75
8 9.109 50.125
9 9 49.125
10 9.672 54.219
Total 95.14 506.562
Average 9.514 50.6562
Time taken to consume x of number message:
Test 1000 Messages (seconds)
1 0.901
2 0.813
3 1.082
4 0.5
5 0.5
6 0.641
7 0.516
8 0.547
9 0.486
10 0.469
Total 6.455
Average 0.6455

Test against integrated system

The flow of sending message is:

web service client --> web service mimic --> JMS

The flow of consuming message is:

listen to the queue in the background

Time taken to produce x number of message:
Test 100 Messages (seconds) 500 Messages (seconds)
1 9.484 47.953
2 9.516 59.375
3 9.593 56.031
4 8.985 46.703
5 9.406 46.953
6 8.906 47.063
7 7.844 54.359
8 9.016 49.094
9 8.859 50.359
10 9.5 51.688
Total 91.109 509.578
Average 9.1109 50.9578
Time taken to consume x number of message:
Test 1000 Messages (seconds)
1 0.899
2 0.892
3 0.447
4 0.609
5 0.547
6 0.75
7 0.584
8 0.5
9 0.585
10 0.515
Total 6.328
Average 0.6328

Summary

One could use this test result to benchmark against the fully integrated system.

Updated by chin-yeh about 14 years ago · 4 revisions