Just checked and the fix is there in 1.1.1-SNAPSHOT Didnt use a big graph as yours can be but didnt see such an overhead possible anymore by default. Think to move forward you will need to share at least an object graph close to yours and potentially a small test doing a persistence with a setup you use - ApplicationComposer can make it easy if you dont know how to write this test.
If too much work sharing few stacks (jstack) during this slowness can maybe help as well - but without guarantees. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2016-01-24 18:18 GMT+01:00 Romain Manni-Bucau <[email protected]>: > canou reproduce and share a sample (gtithub if possible) where it is > visible? > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <http://rmannibucau.wordpress.com> | Github > <https://github.com/rmannibucau> | LinkedIn > <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> > > 2016-01-24 17:10 GMT+01:00 cocorossello <[email protected]>: > >> Hi, >> >> I can confirm that the problem still exists with bval (it performs much >> better but still slow). >> >> The screen is a typical crud screen with a data table and a form to >> create/update. The list is now fast but it takes a few seconds to save the >> entity. The entity has several oneToMany associations marked with cascade. >> >> When I remove bval jars and I put hibernate-validators it only takes 100 >> ms >> or so to save the entity >> >> >> >> -- >> View this message in context: >> http://tomee-openejb.979440.n4.nabble.com/Performance-problems-in-tomee-7-0-0-tp4677292p4677515.html >> Sent from the TomEE Users mailing list archive at Nabble.com. >> > >
