[weld-issues] [JBoss JIRA] Closed: (WELD-522) Weld makes my Java SE app startup time >100x slower
Pete Muir (JIRA)
jira-events at lists.jboss.org
Wed Dec 15 10:41:18 EST 2010
[ https://issues.jboss.org/browse/WELD-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pete Muir closed WELD-522.
--------------------------
Assignee: Pete Muir
Fix Version/s: (was: 1.2.0.Beta1)
Resolution: Duplicate Issue
Consolidating bootstrap performance issues to WELD-446
> Weld makes my Java SE app startup time >100x slower
> ----------------------------------------------------
>
> Key: WELD-522
> URL: https://issues.jboss.org/browse/WELD-522
> Project: Weld
> Issue Type: Bug
> Components: Performance and Scalability
> Affects Versions: 1.0.1.Final
> Environment: Java 6, Weld 1.01 SE + lots of jars on the classpath
> Reporter: Morten Christensen
> Assignee: Pete Muir
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the weld-issues
mailing list