Bug 979436
Summary: | [One-Off] BRMS has performance decrease after applied Roll Up patch BRMS_5.3.1_2_2013 (BZ-953308) | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Alessandro Lazarotti <alazarot> |
Component: | BRE (Expert, Fusion) | Assignee: | Mario Fusco <mfusco> |
Status: | CLOSED NOTABUG | QA Contact: | Lukáš Petrovický <lpetrovi> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | BRMS 5.3.1 | CC: | brms-jira |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-04 15:06:24 UTC | Type: | Support Patch |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 976824 | ||
Bug Blocks: |
Description
Alessandro Lazarotti
2013-06-28 14:01:55 UTC
The problem reported here https://bugzilla.redhat.com/show_bug.cgi?id=969467 was caused by a wrong synchronization pattern that, in order to be fixed, required a change in the policy in how locks are acquired, together with the introduction of a new type of lock. This caused a performance degradation that I partially addressed by tweaking the internal data structures of the before mentioned new lock. Unfortunately I don't see a way to avoid both the deadlock reported in that ticket and the remaining 6% of performance loss reported here. Of course performance is an important feature and we are striving to keep the rule engine as fast as possible, but at the same time we cannot trade correctness for performance. As commented by engineer and after some reviews, a minor loss of performance, which can vary between 3% to 6%, is expected due additional locks needed to fix Bug 969467. This value is not noticeable for most use cases. I am closing this ticket as "not a bug" status. |