Bug 777724 (SOA-240) - Benchmark test: define borders for success
Summary: Benchmark test: define borders for success
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-240
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: QE
Version: 4.2 IR8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 GA
Assignee: Martin Vecera
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-17 15:05 UTC by Martin Vecera
Modified: 2008-02-19 17:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-19 17:05:39 UTC
Type: Task


Attachments (Terms of Use)
soa_performance.ods (8.45 KB, application/vnd.oasis.opendocument.spreadsheet)
2008-01-21 03:28 UTC, Len DiMaggio
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777820 0 high CLOSED CBR using rules has poor performance 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-240 0 None None None Never

Internal Links: 777820

Description Martin Vecera 2007-12-17 15:05:43 UTC
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:

Comment 1 Mark Little 2007-12-17 17:08:54 UTC
Changed the Affects Field, since you can't have an Affects on something we haven't released!

Comment 2 Martin Vecera 2007-12-18 09:30:41 UTC
This was intended as a future item - we will start defining the borders with IR9, so I think it was correct.

Comment 3 Martin Vecera 2008-01-09 11:15:29 UTC
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...

Comment 4 Martin Vecera 2008-01-10 11:23:27 UTC
Win2k3
8: 6.3 msgs/sec with 100 rules - still very bad performance

Comment 5 Martin Vecera 2008-01-16 16:04:43 UTC
RHEL4
8: 19 msgs/sec with 100 rules

Comment 7 Len DiMaggio 2008-01-21 03:28:04 UTC
Attachment: Added: soa_performance.ods


Comment 9 Martin Vecera 2008-01-21 13:12:49 UTC
Link: Added: This issue is related to JBESB-1504


Comment 10 Martin Vecera 2008-01-21 13:19:30 UTC
Link: Added: This issue related SOA-346


Comment 11 Martin Vecera 2008-01-22 10:33:49 UTC
RHEL4 - beta2
1: 233
3: 82
7: 150
8: 20.5 (100 rules)

Comment 12 Martin Vecera 2008-01-22 13:19:33 UTC
RHEL5 - beta2
1: 233
3: 67
7: 150
8: 17.7 (100 rules)

Comment 14 Martin Vecera 2008-01-23 07:43:18 UTC
Win2k3
1: 232
3: 48
7: 131
8: 6.2 (100 rules)


Comment 15 Martin Vecera 2008-01-28 07:21:14 UTC
RHEL4 - CR1
1: 225
3: 80
7: 174
8: 20

Comment 16 Martin Vecera 2008-01-28 07:22:42 UTC
RHEL5 - CR1
1: 220
3: 66
7: 140
8: 18

Comment 17 Len DiMaggio 2008-02-19 17:05:39 UTC
Closing this tracker issue for SOA-P 4.2.0 GA - we'll create new tracking JIRAs as needed for CP1, etc.


Note You need to log in before you can comment on or make changes to this bug.