skip to content

Performance & Tuning

4 roadmaps31 questions

Making Hibernate fast on purpose: JDBC batching, stateless sessions, read-only hints, streaming, and the statistics that prove what SQL actually ran. Interviewers close Hibernate rounds with tuning questions because they expose who has operated the ORM under real load.

part ofHibernateoverview, primer and where to startread it →
on this pageshow

explore

questions

page 2 of 2

For a long-running application using Hibernate, which ORM-level metrics would you actually export to a monitoring system, which would you deliberately leave off, and what does the collection itself cost?

level: principalimportance: nice to knowfreq 24%

basics

~20 s

Export monotonic counters — statements prepared, entity loads/inserts/updates, flushes, transactions and rollbacks, sessions opened versus closed, cache hits/misses/puts per region — and let the backend rate them. Leave off stateful maxima, per-statement logs, and bound parameter values.

open as a page

showing 31–31 of 31