Hibernate Performance Tuning: 10 Common Hibernate Mistakes That Cripple Your Performance

Do you think your application could be faster if you would just solve your Hibernate problems?
Then I have good news for you!
I fixed performance problems in a lot of applications, and most of them were caused by the same set of mistakes. And it gets even better, most of them are easy to fix. So, it probably doesn’t take much to improve your application.
Here is a list of the 10 most common mistakes that cause Hibernate performance problems and how you can fix them.
How to use native queries to perform bulk updates: • Advanced Queries: How ...
If you like this video, please give me your thumbs up and share it with your friends and co-workers.
Like my channel? Subscribe!
➜ bit.ly/2cUsid8
Join the free Member Library:
goo.gl/dtyIIC
Read the accompanying post: www.thoughts-on-java.org/comm...
Want to connect with me?
Blog: www.thoughts-on-java.org/
Twitter: / thjanssen123
Facebook: / thoughtsonjava

[@3asoom11]

Wow! our project has all of the mistakes mentioned used in every part of it :D

[@pravingate6955]

Must needed information!!!

[@zakhard8659]

Very useful! Thanks! The lazy fetch type improves the performance quite a lot, though for me it's a bit less programmer-friendly

[@ThoughtsOnJava]

Hibernate handles the lazy fetching transparently. It's quite user friendly.

[@deepusasidharan2012]

Superb...

[@MiteshSharma]

Yes this is Spring data repository who is making those JOINS him self. Its smart enough to generate those query hints (or any other way) by him self.

[@ThoughtsOnJava]

No, it's a Hibernate feature, but it only adds the JOIN if you use EntityManager.find but not if you're using a JPQL query. That makes it even worse because the fetching behavior becomes inconsistent.
Please see my response to your other comment for more details.

[@deepusasidharan2012]

Ahaa