Consider keeping a constant placeholder instead of the full memory model for classes not indexed ------------------------------------------------------------------------------------------------ Key: HV-589 URL: https://hibernate.onjira.com/browse/HV-589 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.3.0.Final Reporter: Emmanuel Bernard Fix For: 5.x Andrej Golovnin wrote: > After updating JBoss 7 to use the Hibernate Validator 4.3.0 and > adding <property name="javax.persistence.validation.mode" value="NONE"/> > to our persistence.xml file I was able to reduce memory consumption > of SerializableValidatorFactory from ca. 90MB to ca. 256KB. :-) > What I was not able to do, is to avoid loading of Hibernate Validator > and Hibernate Envers at all as we don't use them. Emmanuel's reply If you do not use Hibernate Validator annotations, 90MB might indeed be too much :) Hardy, I wonder if we could optimize the memory model and JPA initialization so that we check if a class has constraints and if it does not, Hibernate Validator keeps a small placeholder to remember that but does not consume any other memory for this non validated class. We could save a lot instead of building the model and keeping it in memory.

Consider keeping a constant placeholder instead of the full memory model for classes not indexed ------------------------------------------------------------------------------------------------ Key: HV-589 URL: https://hibernate.onjira.com/browse/HV-589 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.3.0.Final Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 5.x Andrej Golovnin wrote: > After updating JBoss 7 to use the Hibernate Validator 4.3.0 and > adding <property name="javax.persistence.validation.mode" value="NONE"/> > to our persistence.xml file I was able to reduce memory consumption > of SerializableValidatorFactory from ca. 90MB to ca. 256KB. :-) > What I was not able to do, is to avoid loading of Hibernate Validator > and Hibernate Envers at all as we don't use them. Emmanuel's reply If you do not use Hibernate Validator annotations, 90MB might indeed be too much :) Hardy, I wonder if we could optimize the memory model and JPA initialization so that we check if a class has constraints and if it does not, Hibernate Validator keeps a small placeholder to remember that but does not consume any other memory for this non validated class. We could save a lot instead of building the model and keeping it in memory.

Keep a constant metadata placeholder for unconstrained entities --------------------------------------------------------------- Key: HV-589 URL: https://hibernate.onjira.com/browse/HV-589 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 4.3.0.Final Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 5.0.0.Alpha1 Andrej Golovnin wrote: > After updating JBoss 7 to use the Hibernate Validator 4.3.0 and > adding <property name="javax.persistence.validation.mode" value="NONE"/> > to our persistence.xml file I was able to reduce memory consumption > of SerializableValidatorFactory from ca. 90MB to ca. 256KB. :-) > What I was not able to do, is to avoid loading of Hibernate Validator > and Hibernate Envers at all as we don't use them. Emmanuel's reply If you do not use Hibernate Validator annotations, 90MB might indeed be too much :) Hardy, I wonder if we could optimize the memory model and JPA initialization so that we check if a class has constraints and if it does not, Hibernate Validator keeps a small placeholder to remember that but does not consume any other memory for this non validated class. We could save a lot instead of building the model and keeping it in memory.