James,
We haven't been focused on optimizing memory yet, though I don't
recall any really large in-memory structures in m2eclipse. Here is few
things to look at that might help to isolate the issue:
* what m2eclipse version you are using and what version of Eclipse you
are running?
* what is the size of
<workspace>\.metadata\.plugins\org.maven.ide.eclipse\workspaceState.ser ?
* how much memory Maven reports after building all those modules from
the command line?
* I recommend to use most recent AJDT builds. there is number of memory
and performance improvements in there
* make sure you have "limit console output" checked in Window /
Preferences... / Run/Debug / Console
* with Java 6 you can use jmap and jhat tools to analyze JVM memory dump
and see who is actually eating all the memory. See documentation at
http://java.sun.com/javase/6/docs/technotes/tools/share/jhat.html
The size of the heap dump will be close to the memory size, but if you
can find a way to share such large file, we can look at it for you
regards,
Eugene
James Carman wrote:
I've been trying for hours now to get our multi-level project to
import using m2eclipse. The only way I'm having luck is because I'm
on 64-bit linux and I can jack up my memory settings higher than my
colleagues who are on 32-bit windoze. We use AspectJ, so we would
like to have everything set up for us automatically using AJDT. My
java process for eclipse is taking up 2.6Gb of memory! We have 66
modules in multiple levels (actually only 3 levels, main,
"application" and server/common/client). Has anyone had luck in this
type of environment?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
