In java EE 6, applications have access to Bean Validation. That's why you still
see the reference to the serializable validator factory. 256k seems small
enough, let's not waste time on that.
By the way we need to start bean validation to be sure that your entities are
not validated, so the in
We deliberately chose to optimize hibernate ORM to be fast even if that means a
bit more memory.
We can try and avoid some objects here as there as you propose but I don't
think that would be as beneficial as finding the real culprit between H3 and
H4's memory consumption difference.
On 12 ma
Btw for sure simpleValue should use an arrayList initialized to 1 by default as
it's the most common case.
We might even consider that an array would be better as the final holder even
though there are no agreement in the team yet on the pro/con of arrays vs
collections wrt ease of use, speed a
Even using Lists we could trim those instances which are meant for
long-term purpose; not being very familiar with the code in ORM/HEM
I'm not sure which instances they are, but something among these
lines, when inserted in the right places could provide an easy win:
https://github.com/Sanne/hiber
[thread diverged, not sure how to reply on each point.. so clean sheet:]
I agree as a user it's not simple to deal with two "massindex"
approaches, even worse if they behave differently. Your
straight-forward take on it is to make sure they behave the same, and
I see some good value in it.. still
