Hi, Not much idea with that, it can be linked to a lot of things including scanning exclusions. Since several seconds are lost at startup, can you try to do some jstack (I would try jstack <pid> and jstack -F <pid>) during these moments? Can help to dig into the first level of the analyzis.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2017-01-27 9:51 GMT+01:00 cocorossello <[email protected]>: > Hi, > > Since I upgraded to tomee 7.0.2, from 7.0.1 I can see a signficant > performance degradation, not a stopper, but I'm wondering if this has been > identified. > > I can see that the startup time increases from 27 seconds to 35. And our > end > to end test suite (about 60 parallel phantomjs tests) takes 140 seconds > (from about 120). > > I have no idea of where this may come from, but if I replace openejb-core > with that of 7.0.1 performance is the same again. > > Any ideas? > > > > -- > View this message in context: http://tomee-openejb.979440. > n4.nabble.com/Tomee-7-0-2-performance-tp4680954.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
