Benchmark » History » Version 19
chin-yeh, 07/07/2011 03:32 PM
| 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 | 19 | chin-yeh | See issue #110 for the details on how to benchmark queue systems & web services. |
| 8 | |||
| 9 | 9 | chin-yeh | h2. Test Coverage |
| 10 | |||
| 11 | 1 | chin-yeh | !test_coverage.jpg! |
| 12 | |||
| 13 | 9 | chin-yeh | |
| 14 | h2. Component Used |
||
| 15 | |||
| 16 | 1 | chin-yeh | |_.Name|_.Version| |
| 17 | 4 | chin-yeh | |ecosway-commons|1.4-SNAPSHOT| |
| 18 | |ecosway-adaptor|1.2-SNAPSHOT| |
||
| 19 | |ecwyadaptor|0.5-SNAPSHOT| |
||
| 20 | |ecwyconnector|0.5-SNAPSHOT| |
||
| 21 | |ecwyqconnector-batch|1.4.1-SNAPSHOT| |
||
| 22 | |jms-adaptor|0.7-SNAPSHOT| |
||
| 23 | |soap-adaptor|0.6-SNAPSHOT| |
||
| 24 | 1 | chin-yeh | |us-beans|1.4-SNAPSHOT| |
| 25 | |ws-mimic|2.6.1-SNAPSHOT| |
||
| 26 | |ws-status|1.3-SNAPSHOT| |
||
| 27 | 2 | chin-yeh | |
| 28 | 18 | chin-yeh | h2. Tools |
| 29 | 9 | chin-yeh | |
| 30 | 5 | chin-yeh | * JMeter |
| 31 | 2 | chin-yeh | |
| 32 | 18 | chin-yeh | h2. Result |
| 33 | 1 | chin-yeh | |
| 34 | 12 | chin-yeh | * Summary of this test - [attachment:summary.pdf] |
| 35 | 13 | chin-yeh | * Appendix - [attachment:appendix.pdf] |
| 36 | 15 | chin-yeh | |
| 37 | 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. |