Actions
Benchmark » History » Revision 18
« Previous |
Revision 18/20
(diff)
| Next »
chin-yeh, 07/07/2011 10:49 AM
- Table of contents
- Benchmark
Benchmark¶
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.
Test Coverage¶
Component Used¶
| Name | Version |
|---|---|
| ecosway-commons | 1.4-SNAPSHOT |
| ecosway-adaptor | 1.2-SNAPSHOT |
| ecwyadaptor | 0.5-SNAPSHOT |
| ecwyconnector | 0.5-SNAPSHOT |
| ecwyqconnector-batch | 1.4.1-SNAPSHOT |
| jms-adaptor | 0.7-SNAPSHOT |
| soap-adaptor | 0.6-SNAPSHOT |
| us-beans | 1.4-SNAPSHOT |
| ws-mimic | 2.6.1-SNAPSHOT |
| ws-status | 1.3-SNAPSHOT |
Tools¶
- JMeter
Result¶
- Summary of this test - [summary.pdf]
- Appendix - [appendix.pdf]
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.
Updated by chin-yeh about 13 years ago · 18 revisions