Project

General

Profile

Benchmark » History » Version 17

chin-yeh, 07/07/2011 10:48 AM

1 9 chin-yeh
{{toc}}
2
3 17 chin-yeh
h1. Benchmark
4 1 chin-yeh
5 16 chin-yeh
The purpose of this test is to benchmark the *throughout* and *response time* on a fully integrated system but the *asynchronous/background* processes are not included, e.g. queue consumer.
6 1 chin-yeh
7 9 chin-yeh
h2. Test Coverage
8
9 1 chin-yeh
!test_coverage.jpg!
10
11 9 chin-yeh
12
h2. Component Used
13
14 1 chin-yeh
|_.Name|_.Version|
15 4 chin-yeh
|ecosway-commons|1.4-SNAPSHOT|
16
|ecosway-adaptor|1.2-SNAPSHOT|
17
|ecwyadaptor|0.5-SNAPSHOT|
18
|ecwyconnector|0.5-SNAPSHOT|
19
|ecwyqconnector-batch|1.4.1-SNAPSHOT|
20
|jms-adaptor|0.7-SNAPSHOT|
21
|soap-adaptor|0.6-SNAPSHOT|
22 1 chin-yeh
|us-beans|1.4-SNAPSHOT|
23
|ws-mimic|2.6.1-SNAPSHOT|
24
|ws-status|1.3-SNAPSHOT|
25 2 chin-yeh
26 11 chin-yeh
h2. Test Tools
27 9 chin-yeh
28 5 chin-yeh
* JMeter
29 2 chin-yeh
30 9 chin-yeh
h2. Test Result
31 1 chin-yeh
32 12 chin-yeh
* Summary of this test - [attachment:summary.pdf]
33 13 chin-yeh
* Appendix - [attachment:appendix.pdf]
34 15 chin-yeh
35
When the total size of all messages is over the threshold, the queue system will just drop the new incoming message. It makes the queue system and message recipient(s) (e.g. web service) will not get overloaded.