8:04 a.m.
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
12:41 p.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/jira/browse/WELD-522?page=com.atlassian.jira.plugi...
]
Nicklas Karlsson commented on WELD-522:
---------------------------------------
Is it possible you have loops etc in your injection code that does extra lookups before
resolving? Have you tried making a web app of them to see if it's a Weld general issue
or a Weld SE issue?
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
1:40 p.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/jira/browse/WELD-522?page=com.atlassian.jira.plugi...
]
Morten Christensen commented on WELD-522:
-----------------------------------------
No, I do not do anything special with injection in loops or something like that. My setup
is pretty simple. I only have singletons + one application scoped object and I don't
have providers etc yet as far as I recall.... I BUT as I said the classpath is pretty
involved, so I suspect that weld spends quite some time going through all of them (which I
would like weld NOT to do - if I could only disable this)...Here is a spec from a shell
jar I created:
Class-Path: ../common/libs/runtime-nojee6container/grizzly-webserver-1
.9.18-k.jar ../common/libs/runtime-nojee6container/javax.annotation.j
ar ../common/libs/runtime-nojee6container/javax.inject.jar ../common/
libs/runtime-nojee6container/javax.servlet.jar ../common/libs/runtime
-nojee6container/jersey-bundle-1.1.5.jar ../common/libs/runtime-nojee
6container/jsr311-api-1.1.jar ../common/libs/runtime-nojee6container/
weld-se.jar ../common/libs/runtime-nojee6container/weld-servlet.jar .
./common/libs/runtime/apache-mime4j-0.6.jar ../common/libs/runtime/ar
gs4j-2.0.12.jar ../common/libs/runtime/commons/commons-codec-1.4.jar
../common/libs/runtime/commons/commons-logging-1.1.1.jar ../common/li
bs/runtime/commons/commons-net-2.0.jar ../common/libs/runtime/commons
/commons-net-ftp-2.0.jar ../common/libs/runtime/commons/commons-vfs-1
.0.jar ../common/libs/runtime/google-collect-1.0.jar ../common/libs/r
untime/groovy/groovy-all-1.6.3.jar ../common/libs/runtime/httpclient/
httpclient-4.0.1.jar ../common/libs/runtime/httpclient/httpcore-4.0.1
.jar ../common/libs/runtime/httpclient/httpcore-nio-4.0.1.jar ../comm
on/libs/runtime/httpclient/httpmime-4.0.1.jar ../common/libs/runtime/
javascript/js.jar ../common/libs/runtime/jruby/jruby-complete-1.5.0.R
C2.jar ../common/libs/runtime/json/jackson-core-asl-1.4.3.jar ../comm
on/libs/runtime/json/jackson-jaxrs-1.4.3.jar ../common/libs/runtime/j
son/jackson-xc-1.4.3.jar ../common/libs/runtime/json/jettison-1.2.jar
../common/libs/runtime/rapa-0.9.jar ../common/libs/runtime/scala/jer
sey-scala-1.1.5.jar ../common/libs/runtime/scala/scala-library-2.7.5.
jar ../common/libs/runtime/truezip-6.jar ../common/target/jars/plain/
myapplication-common.jar ../pluginmodules/ftp/libs/runtime/edtftpj.ja
r ../product/api/target/jars/plain/myapplication-api.jar ../product/c
ore/target/jars/plain/myapplication-core.jar ../product/ws/target/jar
s/plain/myapplication-ws.jar
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
1:51 p.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/jira/browse/WELD-522?page=com.atlassian.jira.plugi...
]
Morten Christensen commented on WELD-522:
-----------------------------------------
My app also deploys in glassfish 3 as an web app (it is both a SE and an EE application).
In glassfish it is much harder to judge what the startup cost is but I do not notice any
major slowdowns as for Weld SE (maybe because weld is already initialized in Glassfish
with some of the jars I use ?).
BTW: What is the normal time you guys get between org.jboss.weld.environment.se.StartMain
and firing ContainerInitialized after initialization for medium sized Weld SE apps ?
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
8:05 a.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/jira/browse/WELD-522?page=com.atlassian.jira.plugi...
]
Pete Muir commented on WELD-522:
--------------------------------
Weld should only scan bean archives - i.e. only those bits of the classpath in which there
is a META-INF/beans.xml. It should not look in all your other libraries.
Can you add some timings to the Weld SE bootstrap process to discover which calls are
taking a long time?
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
8:55 a.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/jira/browse/WELD-522?page=com.atlassian.jira.plugi...
]
Morten Christensen commented on WELD-522:
-----------------------------------------
1) Can you suggest a setup for adding the timings you need ?
2) Can you or can you not reproduce a similar delay for other small/medium sized Java SE
applications using Weld SE ?
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
9:33 a.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/jira/browse/WELD-522?page=com.atlassian.jira.plugi...
]
Pete Muir commented on WELD-522:
--------------------------------
1) This is the bootstrap code for Weld SE (in Weld):
bootstrap.startContainer(Environments.SE, deployment, this.applicationBeanStore);
final BeanDeploymentArchive mainBeanDepArch =
deployment.getBeanDeploymentArchives().get(0);
this.manager = bootstrap.getManager(mainBeanDepArch);
bootstrap.startInitialization();
bootstrap.deployBeans();
WeldManagerUtils.getInstanceByType(manager,
ShutdownManager.class).setBootstrap(bootstrap);
bootstrap.validateBeans();
bootstrap.endInitialization();
I would suggest inserting a line between each of these lines that prints out the time
taken for that step as a starting point. Run this two or three times and let us know where
the big delays are.
2) We haven't done any performance work specific to Weld SE.
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
9:15 p.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
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
4:42 a.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/browse/WELD-522?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-522:
--------------------------------
Morten, You don't want this there anyway, so good result ;-)
But seriously, it seems to me then the slowness is coming from the time the JDK takes to
scan the classpath for beans.xml? If we put some timings into the above code, we can
really see what phase is slow.
Weld makes my Java SE app startup time >100x slower
----------------------------------------------------
Key: WELD-522
URL: https://jira.jboss.org/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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 a.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/browse/WELD-522?page=com.atlassian.jira.plugin.sys...
]
Morten Christensen commented on WELD-522:
-----------------------------------------
I also suspect it to be the scanner + java reflection code in Weld. I will do some
profiling on this when we have changed the scanner in Weld SE. If my assumption is
correct, I guess we could easily fix this my letting users configure the names of all the
classes/interfaces that weld should take an interest in (f.x as just a plain list of
qualified names in a text file like services in Java 6). I would love to have this
feature.
Weld makes my Java SE app startup time >100x slower
----------------------------------------------------
Key: WELD-522
URL: https://jira.jboss.org/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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:28 a.m.
New subject: [JBoss JIRA] Commented: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/browse/WELD-522?page=com.atlassian.jira.plugin.sys...
]
Pete Muir commented on WELD-522:
--------------------------------
Morten, absolutely, I was assuming we all though this. What we need to do is isolate
*where* in the code this problem is, as some stuff we can speed up (e.g. reflection) and
some we can't (e.g. scanner).
Weld makes my Java SE app startup time >100x slower
----------------------------------------------------
Key: WELD-522
URL: https://jira.jboss.org/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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:28 p.m.
New subject: [JBoss JIRA] Updated: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/browse/WELD-522?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-522:
---------------------------
Fix Version/s: 1.1.0.Beta2
Weld makes my Java SE app startup time >100x slower
----------------------------------------------------
Key: WELD-522
URL: https://jira.jboss.org/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
Fix For: 1.1.0.Beta2
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:57 a.m.
New subject: [JBoss JIRA] Updated: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/browse/WELD-522?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-522:
---------------------------
Fix Version/s: 1.1.0.CR1
(was: 1.1.0.Beta2)
Weld makes my Java SE app startup time >100x slower
----------------------------------------------------
Key: WELD-522
URL: https://jira.jboss.org/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
Fix For: 1.1.0.CR1
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/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:35 a.m.
New subject: [JBoss JIRA] Updated: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://jira.jboss.org/browse/WELD-522?page=com.atlassian.jira.plugin.sys...
]
Pete Muir updated WELD-522:
---------------------------
Component/s: Performance and Scalability
Weld makes my Java SE app startup time >100x slower
----------------------------------------------------
Key: WELD-522
URL: https://jira.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
Fix For: 1.2.0.Beta1
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
9:41 a.m.
New subject: [JBoss JIRA] Closed: (WELD-522) Weld makes my Java SE app startup time >100x slower
[
https://issues.jboss.org/browse/WELD-522?page=com.atlassian.jira.plugin.s...
]
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
5093
days inactive
5313
days old
14 comments
3 participants
participants (3)
-
Morten Christensen (JIRA) -
Nicklas Karlsson (JIRA)
-
Pete Muir (JIRA)