Build 3417 on linux SLOW

Just downloaded and installed build 3417 on SUSE 9.1 with JDK 1.5-04. Create Project feature is running very slow, and many (most) of the dialog labels are not displaying at all. The input controls on the JDK configuration window are not displaying either, making it impossible to create a project and try any of the editors.

When I run idea.sh from cmd line, I get following output:
Using JVMPI
*** HINT ***: we recommend using Java 5.0 and JVMTI when possible!
Listening on port 10100...

Could that have anything to do with problem?

Am I the only one experiencing this?

14 comments
Comment actions Permalink

Lance Peterson wrote:

Just downloaded and installed build 3417 on SUSE 9.1 with JDK 1.5-04. Create Project feature is running very slow, and many (most) of the dialog labels are not displaying at all. The input controls on the JDK configuration window are not displaying either, making it impossible to create a project and try any of the editors.
Am I the only one experiencing this?


Noticably slower here, as well (Gentoo, kernel 2.6.12, jdk1.5.0.04).
Popup menus take 1-2 seconds to, well, pop-up.
Starting Irida with a bigger initial heap helps somewhat.

Groeten,
Edwin

0
Comment actions Permalink

bump

So why am I getting the message? I'm running with JDK 5, why is it telling me I'm not?

0
Comment actions Permalink

Lance Peterson wrote:

bump

So why am I getting the message? I'm running with JDK 5, why is it telling me I'm not?


Look at that message again...
It's not telling you that you are not using JDK 5, it's telling you that you aren't using JVMTI.

0
Comment actions Permalink

And, despite what YJP says, there's nothing harmful about that. I haven't seen any performance/accuracy differences when profiling with JVMPI instead of JVMTI. Maybe if Anton is around he could explain that to us.

Try taking a few CPU snapshots and sending them to JetBrains. The profiler shouldn't be the culprit.

0
Comment actions Permalink

Why is it telling me I'm running with JVMPI? I thought JVMTI was default in Java 5, and I can't find any settings in idea.sh, idea.vmoptions, or idea.properties that would affect this.

And then there's my original question: Is the JVMPI thing affecting my performance? Because as I said, build 3417 is running unusably slow. I doubled the min and max heap size per Edwin's suggestion, but that didn't help.

0
Comment actions Permalink

Thx Marcus, I'll try that.

0
Comment actions Permalink

Anyways, if you want it to run with JVMTI instead of JVMPI, edit you 'idea.properties' file, and change the line:

-Xrunyjpagent:port=10100

to:

-agentlib:yjpagent=port=10100

0
Comment actions Permalink

Sorry, you should edit "idea.exe.vmoptions", and not "idea.properties"

0
Comment actions Permalink

As per Marcus' suggestion, I've taken a cpu snapshot. I tried uploading to ftp.intellij.net/.uploads, but I keep getting timeout errors. Should I upload somewhere else?

0
Comment actions Permalink

Mail to max@jetbrains.com
-


Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Lance Peterson wrote:

my performance? Because as I said, build 3417 is running unusably
slow. I doubled the min and max heap size per Edwin's suggestion,
but that didn't help.


I'm using this in idea.vmoptions:
-Xms128m
-Xmx512m
-XX:MaxPermSize=92m

Menu's, code analysis (e.g.) isn't as sluggish as they are with the
defaults. Still slower than 3415, but (at least on my box) not unusuably so.

Regards,
Edwin

0
Comment actions Permalink

Marcus Brito wrote:

Sorry, you should edit "idea.exe.vmoptions", and not "idea.properties"


eh, "idea.vmoptions", surely? ;)

Regards,
Edwin

0
Comment actions Permalink

In case anyone's interested, the problem was at my end. I was running dual monitor and the CPU snapshot revealed gobs of time lost in X display calls. I've now switched from xinerama to twinview configuration, and Irida runs much smoother.

Only minor annoyance is that Irida doesn't reposition dialogs and splash screens to keep them from straddling the dual-screen boundary. But that's really minor, IMO.

Thx to Max, Serge, Marcus, and Edwin for help.

0

Please sign in to leave a comment.