[
https://jira.jboss.org/jira/browse/WELD-522?page=com.atlassian.jira.plugi...
]
Morten Christensen commented on WELD-522:
-----------------------------------------
So far I have tried commenting various things out, and I can see I get the biggest
performance boost under Java SE if I remove
"/common/libs/runtime-nojee6container/weld-servlet.jar" from the classpath as
specified above and add a slf4j binding. I don't actually need the weld-servlet jar
under Java SE as I also have the weld-se.jar file. Removing make the application twice+ as
fast to boot up, so now it is only about 50 times slower as it should be :-)
Weld makes my Java SE app startup time >100x slower
----------------------------------------------------
Key: WELD-522
URL:
https://jira.jboss.org/jira/browse/WELD-522
Project: Weld
Issue Type: Bug
Affects Versions: 1.0.1.Final
Environment: Java 6, Weld 1.01 SE + lots of jars on the classpath
Reporter: Morten Christensen
Booting my Java SE app without weld takes << 1s BUT the 1 line for initializing
weld to autowire my app takes at least 4-5 seconds.
My app is not so big and consist of ~20-30 singletons that must be wired + various other
non-weld stuff. I have lots of stuff on my classpath so I suspect that could be why weld
is going crazy.
I guess this could be improved if I can have weld limited to work only inside my own jar
and/or only work with specific classes/packages.
P.S. With breakpoints enabled in a debugger and a bit of unluck, I was even able to have
welds initialization to take ~ 5 minutes one day (reduced to seconds again after I removed
all breakpoints though).
--
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