Bug 1096043
Summary: | [QE] (6.3.0) Performance regression | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Martin Simka <msimka> |
Component: | Hibernate | Assignee: | Brett Meyer <brmeyer> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Simka <msimka> |
Severity: | urgent | Docs Contact: | Russell Dickenson <rdickens> |
Priority: | urgent | ||
Version: | 6.3.0 | CC: | cdewolf, jkudrnac, jmartisk, kkhan, lfuka, maschmid, msimka, pslavice, smumford, theute, zroubali |
Target Milestone: | ER6 | Keywords: | Regression |
Target Release: | EAP 6.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
A regression that can cause performance degradation is present in this release of JBoss EAP 6. It has been traced to the `Statement#getWarnings` method (which was negatively impacted by changes made to resolve an earlier memory leak caused by a bug in the Sybase JDBC drivers).
To address the performance issues, new code has been added to check the log level of warnings and ignore any messages below WARN level. These messages are cleared and not written to the +server.log+ file. While this measure mitigates much of the performance degradation, the issue may still present to varying degrees, depending on the JDBC implementation being used.
To avoid the performance issue completely, users can raise this threshold by setting the `org.hibernate` logging category to ERROR. Care should be taken before making this change, however, as ignoring warnings below the ERROR level can obfuscate possible problems in the database.
|
Story Points: | --- |
Clone Of: | 1094756 | Environment: | |
Last Closed: | 2014-06-28 15:40:26 UTC | Type: | Bug |
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: | |||
Bug Blocks: | 1094756, 1100862 |
Description
Martin Simka
2014-05-09 07:23:45 UTC
1094756 identified two fixes that corrected the performance regression in EAP 6.2.x/ORM 4.2.7.SPx. However, initial tests show that there is still an additional amount of regression in 4.2.13-SNAPSHOT, even with those fixes. We'll continue to evaluate for EAP 6.3 We have updated information on BZ https://bugzilla.redhat.com/show_bug.cgi?id=1094756. It seems that regression is caused by commit a0b01c5483d1f7857c640070b0cafd2c436e5fb5. It turns out that the fixes in https://bugzilla.redhat.com/show_bug.cgi?id=1094756 were sufficient, according to Andrig Miller. This is corrected upstream and will make it into our upgrade next week. *** Bug 1105529 has been marked as a duplicate of this bug. *** verified on EAP 6.3.0.ER7. There is no performance degradation when `org.hibernate` logging category is set to ERROR. Doc text copied from https://bugzilla.redhat.com/show_bug.cgi?id=1094756 which fixed this issue in EAP 6.2.3.CP |