Tags
AeroGear
Arquillian
Bean Validation
Byteman
CDI
Ceylon
Commonhaus
Community
Develocity
Discussions
Eclipse
Elasticsearch
Events
GitHub
HANA
Hibernate Data Repositories
Hibernate OGM
Hibernate ORM
Hibernate Reactive
Hibernate Search
Hibernate Shards
Hibernate Tools
Hibernate Validator
Hiring
Infinispan
Interview
JBoss AS
JBoss Asylum
JBoss Forge
JBoss Tools
JPA
JSF
JSON
JSR 352
Jakarta Data
Jakarta EE
Jakarta Persistence
Java EE
Lucene
MongoDB
MongoDB Extension
Newsletter
Off topic
Performance
PicketLink
Quarkus
Releases
Rich Faces
Seam
Security
Supply Chain
Weld
WildFly
asylum
git
minishift
swarm
Authors
When we profiled our application’s data import pipeline, we expected the bottleneck to be in our business logic — JQ filters, JavaScript evaluation, recursive SQL queries. Instead, Hibernate’s internal JSON handling consumed over 50% of CPU time and allocated 20 GB of unnecessary objects during a routine import of 5 records.
Two small annotation changes fixed it. No code changes, no architectural redesign — just telling Hibernate what it needs to know about how our application uses its data.
As we spent the last year preparing for the first stable release of Hibernate Reactive we have been trying to answer some questions we had.