Using HotSpot Server VM instead of Client VM?
According to the Java Performance FAQ, the HotSpot client VM is for
applications where fast startup times and small memory footprints are
important. The server VM is for applications where overall performance
is more important.
Since I don't start IDEA very often, and I'm developing on a machine
with 1 GB of memory, this would mean that I should run IDEA using the
server VM for optimal performance. But the IDEA JRE only comes with the
client VM. Is this intentional for some reason I've missed, or should I
just copy the server VM into the JRE and run it that way?
Please sign in to leave a comment.
I tried this a few builds ago, for the same reason, but it didn't help.
Starting time was shorter, but other operations were slower.
It could be cause by Swing, receiving less priority on server optimized
VM, but I'm just guessing.
Alain Ravet
Alain Ravet wrote:
Did you make sure that the server VM was used? I tried adding "-server"
as an argument and then I tried changing jvm.cfg but finally I realized
that the IDEA JRE doesn't contain the server VM so the client VM was
used anyway.
Jonas Kvarnstr?m wrote:
> Did you make sure that the server VM was used? I tried adding
"-server"
> as an argument and then I tried changing jvm.cfg but finally I
realized
> that the IDEA JRE doesn't contain the server VM so the client VM was
> used anyway.
Yes, I'm sure : it was in the time before the installer, and the
included jre, when idea.bat was the only way to start idea.
Alain Ravet
Has anyone tried the CMS settings in 1.4?
http://developer.java.sun.com/developer/technicalArticles/Programming/turbo/
1. I'm using it and find it's very good - no pauses between key presses in
the editor specially.
2. Sometimes it completely deadlocks. If you use concurrent gc and idea
deadlocks, don't go posting issues in the tracker about it.
Carlos
I've been running with -XX:+UseConcMarkSweepGC as an experiment. At one
point, IDEA did "lock up"; at the time, the heap was at the -Xmx limit, and
I was getting ~750 millisecond periods of ~100% CPU alternating with ~750
milliseconds of idle CPU. On the hypothesis that the concurrent GC wasn't
being aggressive enough, I've added -XX:CMSInitiatingOccupancyFraction=80 to
the mix. (FYI, there's an interesting article about 1.4.1 GC at
<http://developer.java.sun.com/developer/technicalArticles/Programming/turbo
/>.)
Kendall
"Carlos Costa e Silva" <carlos@keysoft.pt> wrote in message
news:arbjn0$fmc$1@is.intellij.net...
>
in
>
Do you have to use -server to use the -XX options?
/ J
No, it's available in the client vm.