Hi,


i tried bulk insertion of 1000 records using Hibernate .

It took nearly 3 secs for 1000 records insertion.

i already set hibernate.jdbc.batch_size = 1000, still the performace is same.

When i checked the bulk insertion using jdbc , it took just 300MS to insert 1000 records.


Is there any other way to improve the performance of hibernate as if what jdbc does?.


FYI, i am using Hibernate 3.2.5, MySQL 5.0 and java 1.4

Thanks in advance.

nvseenu.

Hm, you may try to disable all sorts of caching, but honestly speaking, hibernate may not be the right tool for bulk data processing.

Thanks Thomson.

even i tried by disabling second level cache , still the performance is same.


Is that happening because of Hibernate trying to get primary key from db and populate it into id field of persistent class during/after bulk insertion ?.

During bulk insertion using jdbc, i never keen on getting primary keys of inserted records and populating to id fields , mainly focus on whether they have been inserted successfully.


However, your suggestion is helpful for me.

So for bulk insertion , we have to depend on hand coded jdbc. am i right ?

Thanks,
nvseenu

That is probably one of the reasons. (depends on what db you use) If you really want to dig deep into the problem, you could use profiling tools to check where hibernate/the data base burns most of the time during the process.


Yep, I would do. Hibernate is programmed very well (from what few I have seen from the source code), but nothing will beat straight forward hand written code that just fills prepared statements and executes them.

The problem is not in using the second-level-cache, it's hibernate's first-level-cache aka persistence-context (pc).

hibernate will keep all of your 1000 inserted objects in the pc, so when doing mass-operations it's necessaryto clear the persistence-context in regular intervals (like every 50 inserts) via session.flush() and session.clear().

This will speed things up considerably, so hibernate could be used for the job. But overall Thomson is right, hibernate is not the best tool for these tasks.

For bulk operations it is usually better to use the stateless session.
But then you dont have a lot of other features like dirty checking.

ideally, don't do this via hibernate.