Hide Forgot
Date of First Response: 2007-12-17 12:08:54 project_key: SOA To SOA-P benchmark test (for instance http://testify.test.redhat.com/testplans.cgi?op=view&id=516) define when the test case should be marked as passed. Performance 1: > 100 msg/s Performance 2: Performance 3: Performance 4: Performance 5: Performance 6: Performance 7: Performance 8:
Changed the Affects Field, since you can't have an Affects on something we haven't released!
This was intended as a future item - we will start defining the borders with IR9, so I think it was correct.
Last results from working tests (see Hudson). The numbers are in messages per sec. RHEL4 1: 235 3: 78 7: 149 8: 3.8 - CBR, 1000 rules (~150 kB file) - poor performance! RHEL5 1: 225 3: 67 7: 138 8: 2.6 Win2k3 1: 218 3: 48 7: 129 8: We can't expect anything surprising here...
Win2k3 8: 6.3 msgs/sec with 100 rules - still very bad performance
RHEL4 8: 19 msgs/sec with 100 rules
Attachment: Added: soa_performance.ods
Link: Added: This issue is related to JBESB-1504
Link: Added: This issue related SOA-346
RHEL4 - beta2 1: 233 3: 82 7: 150 8: 20.5 (100 rules)
RHEL5 - beta2 1: 233 3: 67 7: 150 8: 17.7 (100 rules)
Win2k3 1: 232 3: 48 7: 131 8: 6.2 (100 rules)
RHEL4 - CR1 1: 225 3: 80 7: 174 8: 20
RHEL5 - CR1 1: 220 3: 66 7: 140 8: 18
Closing this tracker issue for SOA-P 4.2.0 GA - we'll create new tracking JIRAs as needed for CP1, etc.