[jbosstools-issues] [JBoss JIRA] (JBIDE-15398) CDI Builder is sloooow

Mon Sep 16 19:39:03 EDT 2013

    [ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804866#comment-12804866 ] 

Viacheslav Kabanovich edited comment on JBIDE-15398 at 9/16/13 7:38 PM:
------------------------------------------------------------------------

I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above). 
When run with 1Gb memory, build stuck at 83%, memory usage is shown in 
!MemoryUsedWithNewMaven.png|thumbnail!

Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.
I had to kill Eclipse.

When run with 1.5Gb, build stuck at 100%, I had to kill Eclipse again.

When run with 1.8Gb, build passed in 10 minutes, on the verge of memory. I did a few modifications on files, then clean build on a few projects. After that I might believe that Maven released some memory used in build of workspace. Memory usage after all builds were completed is shown in
!MemoryUsedWithNewMavenAfterBuild.png|thumbnail!
It seems that Maven still keeps all grabbed memory.

My general impression is that Maven 1.5 takes *more* memory than Maven 1.4. With maven 1.4 I was able to do clean/build of wildfly workspace in 5 minutes.

      was (Author: scabanovich):
    I run clean/build of wildly workspace on Eclipse with Maven 1.5.0 (link above). 
When run with 1Gb memory, build stuck at 83%, memory usage is shown in !MemoryUsedWithNewMaven.png|thumbnail!

Maybe new Maven does not have memory leak now, and releases memory, but it uses it a lot while building.

> CDI Builder is sloooow
> ----------------------
>
>                 Key: JBIDE-15398
>                 URL: https://issues.jboss.org/browse/JBIDE-15398
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi
>    Affects Versions: 4.1.0.Final
>         Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25
>            Reporter: Fred Bricon
>            Assignee: Viacheslav Kabanovich
>            Priority: Critical
>             Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
>         Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt, MemoryUsedOnWildflyBuild.png, MemoryUsedWithNewMaven.png, MemoryUsedWithNewMavenAfterBuild.png
>
>
> After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator.
> 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar.
> If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the bulk of JBT), import+build complete in ~12/13 min

--
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