1 of 1 people found this helpful
Did you also try running the test without Envers, to see if the huuuge performance hit because of the lack of clear() is because of Envers? If it turns out it is, please report a bug, as this should not have an impact.
Clear() essentialy detaches all entities and makes them available for GC; but usually you have one EntityManager for one transaction, max several transactions.
Yes, I "turned off" Envers for both scenarios. It took about 30 min for both. I will report a bug.
For 100,000 editions:
6h (without clear)
3min (with clear)
For 1,000,000 editions:
too slow to test (without clear)
30min (with clear)
Thanks for the data!
Now we only need to investigate what's wrong ...