Slow editor, project view in Maia M1 - 10369

A few builds ago of Maia I switched to Java 6, when the Java update arrive. It was really fast. These are my settings:

<key>VMOptions</key>                                                                                                  
<string>-Xms256m -Xmx1024m -XX:MaxPermSize=800m -Xbootclasspath/a:../lib/boot.jar -ea -agentlib:yjpagent=disablej2ee</string>



 


Since I'm using Maia M1 - 10369 the editor, even scrolling on the project view is very, very slow. Code completion also.

I switched to Java 5, but it's the same behaviour.

What can I do to solve this problem or how can I help you to do it in the next build?

Another issue is, that IDEA 9 needs about 2 times more memory to run GWT project than IDEA 8.

Thanks

9 comments
Comment actions Permalink

I am experiencing similar issues. Slow scrolling, slow code completion, delays in windows getting focus after clicking on them, and delays sometimes when typing in the editor. I've simply attributed them to standard (early) EAP behavior as new features are introduced and other changes have been made, but not yet optimized. But it probably would be good to have them at least basically resolved before an official M1 release. (10369 is, I believe, an M1 Release Candidate)

0
Comment actions Permalink

As I wrote, previous build of Maia were really fast. Just this build is very, very slow. My fingers are faster than IDEA :/

0
Comment actions Permalink

Hello Mark,

I am experiencing similar issues. Slow scrolling, slow code
completion, delays in windows getting focus after clicking on them,
and delays sometimes when typing in the editor. I've simply attributed
them to standard (early) EAP behavior as new features are introduced
and other changes have been made

, but not yet optimized. But it probably would be good to have them at
least basically resolved before an official M1 release. (10369 is, I
believe, an M1 Release Candidate)


Could you please file a JIRA issue and attach a CPU snapshot?

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hello Leszek,

As I wrote, previous build of Maia were really fast. Just this build
is very, very slow. My fingers are faster that IDEA :/


Could you please file a JIRA issue and attach a CPU snapshot?

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

I had this problem. My analysis showed that most often the delays are due to garbage collector stopping the world. It's another story why IDEA creates so many objects.

So, running on JDK 6 Update 14 I have the following idea.exe.vmoptions:

-XX:+UnlockExperimentalVMOptions
-XX:+UseG1GC
-XX:MaxGCPauseMillis=2000
-XX:GCPauseIntervalMillis=5000
-XX:+G1ParallelRSetUpdatingEnabled
-XX:+G1ParallelRSetScanningEnabled
-XX:+DoEscapeAnalysis
-XX:+AggressiveOpts
-Xms256m
-Xmx768m
-XX:MaxPermSize=150m


And things are pretty smooth. Key points:

  1. You must be running JDK 6 Update 14, as this is the release that got the new G1 garbage collector.
  2. G1 GC is not officially supported by Sun/Oracle in production without a support contract. But what developer cares?
  3. Key timing options here are:
    -XX:MaxGCPauseMillis=2000
    -XX:GCPauseIntervalMillis=5000

The first is a hint to limit the time slot a G1 can take over, e.g. what's your desired 'wait-time' while it does the compaction/collection. Most of the time G1 adheres to it, but again, it's a hint only. The other option is setting the interval between G1 runs, so as to not kill the system with GC activity.

The rest of the options are various performance optimizations, which may or may not render your system less stable. I personally didn't have any noticable problems, enjoying the ride.

HTH,
Andrew

0
Comment actions Permalink

I tried IDEA with very similiar settings and I would get a VM crash every
10-20 minutes due to the G1 collector :(

I had this problem. My analysis showed that most often the delays are
due to garbage collector stopping the world. It's another story why
IDEA creates so many objects.

So, running on JDK 6 Update 14 I have the following
idea.exe.vmoptions:

-XX:+UnlockExperimentalVMOptions
> -XX:+UseG1GC
> -XX:MaxGCPauseMillis=2000
> -XX:GCPauseIntervalMillis=5000
> -XX:+G1ParallelRSetUpdatingEnabled
> -XX:+G1ParallelRSetScanningEnabled
> -XX:+DoEscapeAnalysis
> -XX:+AggressiveOpts
> -Xms256m
> -Xmx768m
> -XX:MaxPermSize=150m

And things are pretty smooth. Key points:

1. You must be running JDK 6 Update 14, as this is the release that
got the new G1 garbage collector.

2. G1 GC is not officially supported by Sun/Oracle in production
without a support contract. But what developer cares?

3. Key timing options here are:

-XX:MaxGCPauseMillis=2000
>
> -XX:GCPauseIntervalMillis=5000


The first is a hint to limit the time slot a G1 can take over, e.g.
what's your desired 'wait-time' while it does the
compaction/collection. Most of the time G1 adheres to it, but again,
it's a hint only. The other option is setting the interval between G1
runs, so as to not kill the system with G

C activity.

The rest of the options are various performance optimizations, which
may or may not render your system less stable. I personally didn't
have any noticable problems, enjoying the ride.

HTH,
Andrew
---
Original message URL:
http://www.jetbrains.net/devnet/message/5240846#5240846



0
Comment actions Permalink



I tried IDEA with very similiar settings and I would get a VM crash every
10-20 minutes due to the G1 collector :(


Chris, have you tried limiting it only to G1 settings? Things like escape analysis are still a WIP. So, basically, try with only G1 pause times (and -X unlock experimental features) switches, and drop all others. Also, was it with a final JDK 6 Update 14 release? G1 failed with IDEA for me too, but that was way before, when Update 14 was still in EAP.

HTH,
Andrew

0
Comment actions Permalink

Hi Andrew,

Yes I've tried u14 final with just the G1, no dice for me unfortunately.
Remember that as far as Sun are concerned the G1 isn't production ready yet
either and (from my experience at least) I'm inclined to agree. Looks like
you've been fortunate enough to get a stable config but I've given up for
now and am happy to sit back and wait until it is considered stable. Full
index rebuilds after a crash are pretty disruptive to my productivity and
I haven't been suffering much from GC problems anyway.

Cheers,
Chris


>
> I tried IDEA with very similiar settings and I would get a VM crash
> every 10-20 minutes due to the G1 collector :(
>
>


Chris, have you tried limiting it only to G1 settings? Things like
escape analysis are still a WIP. So, basically, try with only G1 pause
times (and -X unlock experimental features) switches, and drop all
others. Also, was it with a final JDK 6 Update 14 release? G1 failed
with IDEA for me too, but that was way before, when Update 14 was
still in EAP.

HTH,
Andrew
---
Original message URL:
http://www.jetbrains.net/devnet/message/5240850#5240850



0
Comment actions Permalink

You have it in the attachment. Please look also on the GWT compiler. It takes long time to run the app. Sometimes it looks like the GWT shell is freezing for a while.



Attachment(s):
10369_leszek_26.06.2009_16.13.25.zip
0

Please sign in to leave a comment.