Hi Neale,
well you find a big part of the overhead: the scanning, you can add all
which is not done by tomcat (JPA, EJB init, CDI...). Well maybe tomcat +
webapp startup should be compared to a tomee + webapp startup.
you spoke about multithreading which seems to be a good idea but it can
lead
without synchro issues?
I'm doing some work with Yourkit next to dig a bit deeper.
Best Regards,
Neale
- Original Message -
From: Romain Manni-Bucau rmannibu...@gmail.com
To: users@openejb.apache.org
Sent: Monday, April 16, 2012 1:51 AM
Subject: Re: TomEE startup performance
Hi Neale
...@gmail.com
To: users@openejb.apache.org
Sent: Monday, April 16, 2012 1:51 AM
Subject: Re: TomEE startup performance
Hi Neale,
well you find a big part of the overhead: the scanning, you can add all
which is not done by tomcat (JPA, EJB init, CDI...). Well maybe tomcat +
webapp startup should
: TomEE startup performance
yep, the scanning on big apps is the place to optimize. that's why we
created the scan.xml file.
that part is in xbean (subproject of geronimo) and it should be optimized
there, not in openejb (even if some bridge can let us do it in openejb if
we dont want to wait
,
Neale
- Original Message - From: Romain Manni-Bucau
rmannibu...@gmail.com
To: users@openejb.apache.org
Sent: Monday, April 16, 2012 2:20 AM
Subject: Re: TomEE startup performance
yep, the scanning on big apps is the place to optimize. that's why we
created the scan.xml file
Hi Guys,
Could someone explain in some more detail what exactly causes the slower
startup time in TomEE compared to Tomcat?
I imagine it's parsing classes, annotations etc.. but haven't looked at that
area of the code too much yet.
One thing I've noticed in our testing, is that it seems to be
