Hide Forgot
Date of First Response: 2007-11-05 14:23:15 project_key: SOA Mark sais: Once ESB 4.2.1 has GA-ed later today, our focus will turn to getting the platform out on time (17th of December). Amongst other things, one of the areas we could really do with help is on stressing the platform as a whole and checking that it does what it says it does! In HP we used to have something called a test-a-thon for each product release, where the entire middleware division would devote some time to stressing the next release of a product. How much time depended on the individuals and groups, but even a few hours often brought valuable feedback that assisted the product and QA. It would be good if you could plan with your teams some time over the next few weeks to go through the next beta of the platform, testing your own project's integration as well as others. If this works out and there's enough interest, maybe we could extend this to the individual projects.
Link: Added: This issue is related to SOA-85
Can you point me to the branch/build instructions for the release that should be tested? Are there any constraints on how these tests need to be executed? As a one shot or automated?
Attachment: Added: PerformanceAnalysis_WS.2.0.1_SP2.odt
I've tested against the following ESB version: URL: https://svn.labs.jboss.com/labs/jbossesb/branches/JBESB_4_2_1_GA_CP Repository Root: https://svn.labs.jboss.com Repository UUID: c60d74c8-e8f6-0310-9e8f-d4a2fc68ab70 Revision: 16627 Please see the results attached.
My results have been using a manual setup and execution of the test cases. For future runs, we need to integrate with the ESB QA environment to run them in an automated fashion.
Attachment: Added: benchmark_suite.zip
Attachment: Added: ws_performance_test_invm.odt
Link: Added: This issue related SOA-877