Bug 473496

Summary: Performance regression in broker management
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-cppAssignee: Ted Ross <tross>
Status: CLOSED ERRATA QA Contact: Kim van der Riet <kim.vdriet>
Severity: high Docs Contact:
Priority: urgent    
Version: 1.1CC: freznice
Target Milestone: 1.1   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-02-04 15:35:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gordon Sim 2008-11-28 20:55:35 UTC
A 40-50% regression in performance of the broker was introduced by r719699[1]. It is an issue with the management and can be avoided by turning management off (-m false).

(My guess - speculative - is that its due to more frequent use of the qpid::sys::now() function).

[1] http://svn.apache.org/viewvc?rev=719699&view=rev

Comment 1 Ted Ross 2008-12-01 17:16:00 UTC
This regression has been fixed in the upstream revision r722120.

Comment 3 Frantisek Reznicek 2008-12-05 11:02:16 UTC
Performance issue has been fixed. Running qpidd with and without management enabled provide now close comparable perftest results:

RHEL 5.2 (dhcp-lab-200)
starting qpidd with management on
starting qpidd with management off
summary
.with management
78004.3 72638.1 146076 142.652
.without management
78203 76793.5 153621 150.02


RHEL 4.7 (nec-em15)
starting qpidd with management on
starting qpidd with management off
summary
.with management
25815.3 25703.2 51603.2 50.3938
.without management
27150.8 27026.8 54270 52.9981


Validated on RHEL 5.2 / 4.7, i386 / x86_64 on packages: qpidd-0.3.722891-2.el5, rhm-0.3.2913-1.el5

->VERIFIED

Comment 5 errata-xmlrpc 2009-02-04 15:35:54 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-0035.html