[
https://issues.jboss.org/browse/JBIDE-16286?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-16286:
------------------------------------------
so here are my build times:
* Eclipse: Kepler Service Release 1, Build id: 20130919-0819
* sun jdk 1.7u45
* m2e: org.eclipse.m2e.core_1.5.0.20131218-1213
* cdi: org.jboss.tools.cdi.core_1.6.0.Alpha1-v20131214-0017-B524
* undertow and wildfly both present in my workspace.
* Change <version.io.undertow> (in wildfly-parent/pom.xml) from 1.0.0.Beta26 to
1.0.0.Beta29:
* only m2e, without CDI:
** start:21:22:46 CET
** stop 21:27:52 CET
* m2e + CDI:
** start: 21:39:48
** stop: 21:46:13
weird, looks like I cannot reproduce this in a new and fresh Eclipse with sun-jdk 1.7u45
where I only have added m2e and cdi.
CDI builder (not import, workspace rebuild) is very slow in wildfly
-------------------------------------------------------------------
Key: JBIDE-16286
URL:
https://issues.jboss.org/browse/JBIDE-16286
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Affects Versions: 4.1.1.Final
Reporter: Andre Dietisheim
Assignee: Viacheslav Kabanovich
Priority: Critical
Labels: performance
Fix For: 4.1.2.Final, 4.2.0.Alpha2
Attachments: cdi-builder.ogv, cleanBuild.png,
maven-preferences-hide-children.png, thread-dump-7_05.txt, thread-dump-7_19.txt,
updatingPom.png, VisualVM 1.3.2 _083.png
When working in a wildfly workspace with all wildfly projects imported and CDI builder
enabled, workspace rebuilds (that you trigger by changing poms and then do maven update
project) are a lot slower than without it. Re-building the whole workspace can easily take
up to 20 minutes for me.
Hard to give more general purpose details, I did a quick screencast to give an impression
how slow things are for me.
[^cdi-builder.ogv]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira