The thread, http://forum.hibernate.org/viewtopic.ph ... highlight=, talks about improving the performance for saving 20,000 objects.

One responder said that not having a transaction could be an issue and then recommended creating a transaction and committing the transaction every 100 or so saves. Paul Hatcher responded that one should also perform an Evict of the objects after committing the transaction (the commit results in a flush). This is logical b/c less objects for nHib to check the dirty flag.

However, I don't understand why breaking the Save into multiple transactions is performant. If there's enough memory and we start a single transaction to save 20,000 objects, how is this less performant than breaking up the save of these objects to where we commit a transaction every 100 or so?

Thanks very much --
Bill (metazone)