Forget about the 500 transactions. The problem is this: with 300-500 objects in the session cache, a single transaction( with an single object inserted) takes about one second.
It simply does *not* take a second to dirty check 500 objects, dude. Nowhere even close. If you think you can prove that it does, send my the code to demonstrate this. It would have to be some kind of bug.
But it doesn't.
Well, it is actually normal and correct to use a different session for each transaction. But, nevertheless, dirty checking 500 objects doesn't take a second.I am thinking of this idea: Using a session to load object only(read-only session). Use a new session for every transaction just make sure that there is no object is cached in the session.
------------------------------------------------------- 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
