Way to increase the memory for IntelliJ

I have plenty of left over ram but IntelliJ seems to only use 128 megs and
then does a garbage collection which freezes the whole app for a few
seconds. I tried changing my shortcut to
C:\IntelliJ-IDEA-4.1\bin\idea.exe -Xms128m -Xmx384m but it doesn't look like
it affects the amount of memory IntelliJ is allowed to use.

Any ideas?

Thanks,
Grant Gochnauer
http://www.gochnauer.org


4 comments
Comment actions Permalink

Hi,

Edit lax.nl.java.option.additional property value in idea.lax config file

Grant Gochnauer wrote:

I have plenty of left over ram but IntelliJ seems to only use 128 megs and
then does a garbage collection which freezes the whole app for a few
seconds. I tried changing my shortcut to
C:\IntelliJ-IDEA-4.1\bin\idea.exe -Xms128m -Xmx384m but it doesn't look like
it affects the amount of memory IntelliJ is allowed to use.

Any ideas?

Thanks,
Grant Gochnauer
http://www.gochnauer.org



--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

This doesn't seem to change the behavior. I set the max memory from 192 to
384 and the garbage collection still happens around 128 meg.

---Grant


"Grant Gochnauer" <ggochnauer@braunconsult.com> wrote in message
news:cb9mv3$s5d$1@is.intellij.net...

I have plenty of left over ram but IntelliJ seems to only use 128 megs and
then does a garbage collection which freezes the whole app for a few
seconds. I tried changing my shortcut to
C:\IntelliJ-IDEA-4.1\bin\idea.exe -Xms128m -Xmx384m but it doesn't look

like

it affects the amount of memory IntelliJ is allowed to use.

>

Any ideas?

>

Thanks,
Grant Gochnauer
http://www.gochnauer.org

>
>


0
Comment actions Permalink

Keep in mind that increasing the memory can be a double edged sword. While it may cause garbage collection to occur less frequently, when it does happen it takes longer and thus increases the time that IDEA is frozen. The key is to find a nice balance between not too frequent, but still quick GC. :) I personally find it more favorable to have quicker GC, even if it happens more frequent.

0
Comment actions Permalink

And that's the intent of GC tuning. It's ok to have lots of short constant
GCs, partial gc, but the problem most are seeing are full GCs which always
take longer.

The only way to figure out what setting you need is to spend a little time
tracking GC with various settings and graphing it. While I don't do this
for IDEA, I do it for java app servers to see if various settings improve gc
over time, and reduce full GCs.

Every machine, memory, OS and JVM combination will be different. Throwing
more memory at a java app is not always the solution... This is most likely
why JB doesn't tweak settings more, too many variables to take into account.

R


On 6/22/04 6:21 PM, in article
8491571.1087942906026.JavaMail.itn@is.intellij.net, "Mark Vedder"
<no_mail@jetbrains.com> wrote:

Keep in mind that increasing the memory can be a double edged sword. While it
may cause garbage collection to occur less frequently, when it does happen it
takes longer and thus increases the time that IDEA is frozen. The key is to
find a nice balance between not too frequent, but still quick GC. :) I
personally find it more favorable to have quicker GC, even if it happens more
frequent.


0

Please sign in to leave a comment.