[Hibernate-issues] [Hibernate-JIRA] Closed: (HB-355) only save the explicitly mentioned object during flush

[<leg...@at...>]

Message:

   The following issue has been closed.

   Resolver: Gavin King
       Date: Tue, 23 Sep 2003 9:44 AM

As I told you in the mailing list, you are just plain WRONG. It does not take 1 second to dirty check 600 objects. This is an absurd number; I can dirty check 10 000 objects in that time, and I have the tests to prove it.

Please take some time to learn how to do proper performance profiling in a hotspot JVM.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-355


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-355
    Summary: only save the explicitly mentioned object  during flush
       Type: New Feature

     Status: Closed
   Priority: Major
 Resolution: REJECTED

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.2

   Assignee: 
   Reporter: jason zhang

    Created: Tue, 23 Sep 2003 4:31 AM
    Updated: Tue, 23 Sep 2003 9:44 AM

Description:

When the session is commit, hibernate does a dirty check on every object in the session cache.  Although it is claimed that the dirty check is effecient, it costs more than 1 second somtime to dirty check 600 objects in session in my system.  I tried various of performance tuning, but no luck. 
I'd rather to see the dirty check behavior can be turned on or off through a configuration parameter or session attribute. For example, if I set the hibernate.dirtyCheck=false in hibernate.cfg.xml, the hibernate would not check the objects in session cache, but only perform persistence for the objects which user metioned explicitly through session.save(), session.update(), session.saveOrUpdate() and session.delete(), and the objects that are cascaded from these objects.

If given appropriate instruction/direction, I would like to implement this feature.

jason




---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira