My system is a prototype system. There is only one test user at any time. For this user, there is about 500-600 objects loaded in the Hibernate session at maximal. Very often, my application needs to change only one field in one object and commit the transaction. My code is like this
Tranaction tx=sessiob.beginTransaction(); foo.setField(newValue); tx.commit(); However the modification and commit logic need to repeat about 500 times before the control is returned to user. I found the performance is really bad. One transaction take about one second. It takes about 10 minutes to finish the whole modification logic. This performance is intolerable. 1. When the commit() is called, will the hibernate loop through every object in the session and check for modification? 2. If it does, is it an expensive operation? Any suggestion to solve the performance bottleneck in my situation is really appreacited. Should I use SQL directly instead of Hibernate to do the commit for this case? jason __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
