[
https://jira.jboss.org/jira/browse/EJBTHREE-1800?page=com.atlassian.jira....
]
jaikiran pai commented on EJBTHREE-1800:
----------------------------------------
The attached cinco application deployed within a few seconds on my setup. So i created a
sample application (myejb.jar attached with 100 EJBs). On my test setup i keep increasing
the number of beans in this application for testing. Initially the tests were against
5.0.1 GA to get some timings against that. During this testing against 5.0.1 GA there were
some issues that were discovered (JBMICROCONT-421 and EJBTHREE-1798) . Both have been
taken care off.
At this point, i have been testing this against 5_x branch to see the improvements and
check for any other bottlenecks. We have found one in AOP which is being discussed (and we
have a workaround to this).
The other one that we found is related to MC's aggressive scanning of MC beans for
annotations. I am going to open a forum thread to discuss a possible optimization in the
MC code, which has shown good results on my test setup with JProfiler. Attached with this
JIRA are the "before" and "after" snapshots from the profiler.
Improve EJB3 deployment time on AS5
------------------------------------
Key: EJBTHREE-1800
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1800
Project: EJB 3.0
Issue Type: Task
Affects Versions: 1.1.3
Environment: JBossAS5.x
Reporter: jaikiran pai
Assignee: jaikiran pai
Attachments: cinco.zip, MCAnnotationPlugin_AFTER, MCAnnotationPlugin_BEFORE
Many users have reported that EJB3 deployment on AS5 is relatively very slow compared to
AS4. The referenced forum thread provides some good information about where the time is
spent in a sample application.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira