[hibernate-issues] [Hibernate-JIRA] Created: (HHH-5062) In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data
Fabiano Cury (JIRA)
noreply at atlassian.com
Thu Apr 1 14:43:31 EDT 2010
In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data
-----------------------------------------------------------------------------------------------
Key: HHH-5062
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5062
Project: Hibernate Core
Issue Type: Improvement
Components: core
Affects Versions: 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.7, 3.2.6
Environment: Linux / DB2 / version 3.2.6 and above
Reporter: Fabiano Cury
Attachments: issueHibernate.JPG
When the flush method is called this method call the onFlush method of class DefaultFlushEventListener and then the method flushEverythingToExecutions(event).
This method (flushEverythingToExecutions) call many times (loop) the method log.isDebugEnabled().
This cause a big overhead in this method.
I suggest you to put an attribute in the method flushEverythingToExecutions(flushEverythingToExecutions(FlushEvent event, Boolean isDebugEnable) and verify this attribute before the loop for.
Attached the print screen of profiling that help me to detect this issue.
Tks.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list