Batch fetching in Devicon: eliminating N+1 queries for lazy collections
When looping over a collection of posts, lazy loading causes an N+1 query problem; using Hibernate @BatchSize reduces queries dramatically and improves performance.
Loading…
ReadMeFeed / Community knowledge
#batch-fetching
Real questions. Useful conversations. Find the people who know your stack.
hibernateHarvesting Large Result Sets in Hibernate Without Loading the World Into Memory
Use fetchSize with ScrollableResults and batch fetching to harvest large Hibernate result sets without loading everything into memory, while avoiding cursor leaks and N+1 queries.
Cutting N+1 Queries in Hibernate with @BatchSize: A Practical Guide
Learn how Hibernate’s @BatchSize annotation can reduce N+1 queries by batching lazy loads, avoid cartesian products, and keep result sets manageable. Follow a practical example, trade‑offs, and a step‑by‑step checklist to implement it safely.
Reduce N+1 Selects in Hibernate with Batch Fetching
Configure Hibernate @BatchSize and hibernate.default_batch_fetch_size to load lazy associations in groups instead of one query per row.
javaHibernate @BatchSize differs between H2 and PostgreSQL in 6.2
Goal Enable identical @BatchSize‑driven batch fetching when running Hibernate 6.2 against an in‑memory H2 database locally and against a production PostgreSQL instance. Constraints The Hibernate documentation notes that batch fetching effectiveness is dialect‑dependent and requires the JDBC driver to support statement rewriting (rewriteBatchStatements=true)
xd