# Session Factory Initialization time massively increased

**URL:** <https://discourse.hibernate.org/t/session-factory-initialization-time-massively-increased/11966>\
**Category:** Hibernate ORM\
**Created:** [November 10, 2025, 4:10am UTC](https://discourse.hibernate.org/t/session-factory-initialization-time-massively-increased/11966 "2025-11-10T04:10:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![beikov](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.hibernate.org/beikov/32/258_2.png) [@beikov](https://discourse.hibernate.org/u/beikov)\
**Post date:** [November 10, 2025, 12:13pm UTC](https://discourse.hibernate.org/t/session-factory-initialization-time-massively-increased/11966/2 "2025-11-10T12:13:15Z")

</div>

Like I already told you [here](https://discourse.hibernate.org/t/using-custom-bytecodeprovider-in-hibernate-6/7160/6), there can be many different reasons for this behavior.  
Clearly, the boot time is related to the amount of entities, because the more entities Hibernate ORM has to analyze, the more processing needs to happen.

You can customize `BytecodeProvider` if you want, but I doubt that it has to do with that. The easiest way to figure this out, is to just use build time bytecode enhancement and see if that improves your startup time.

---

_[View the full topic](https://discourse.hibernate.org/t/session-factory-initialization-time-massively-increased/11966)._
