47 comments
Comment actions Permalink

Ash, that seems kind of odd to do this since you're just measuring startup,
but the VM will cache some of these objects, so try a loop or something and
test that, I would say pay attention to real world use, not just a short
test case. I understand 1.3.1 starts up faster, but in the long run is it
making efficient use of the object, or is 1.4.2 better at it?

R

"Ash Searle" <no_mail@jetbrains.com> wrote in message
news:8875330.1057164872125.JavaMail.itn@is.intellij.net...

I was hoping that too, but just did a simple test and was sorely

dissapointed. The class below just constructs a JFileChooser, and is
consistenly so much slower for 1.4 (1.4.1 and 1.4.2) it's just not funny:

> public class FileC {
>     public static void main(String args[]) {
>         new JFileChooser();
>         System.exit(0);
>     }
> }
> ]]>

>

Running it with 1.3.1 is consistenly quicker, and the only thing I can

think of is it being down to that 'Look in' drop-down. Quick figures for
difference are that on my file system the code above has never taken more
than 5 seconds from a cold start under 1.3.1, whereas it repeatedly takes
around 30 seconds under 1.4. Something somewhere is clearly still wrong.


0
Comment actions Permalink

If somebody really wanted to try IDEA with 1.4.2 write a class like:


Run this class with jdk1.4.2 (with correct classpath off course) and there you go IDEA with 1.4.2 :)
(I had the JFileChooser problems before and they toatlly vanished with 1.4.2)

Another way to solve JFileChooser problems is to take a stack dump when it occurs and post it here so the Intellij guys can help you :)

In my case it was the java.net.URL.hashcode method that was doing strange stuff see:

http://www.intellij.net/tracker/idea/viewSCR?publicId=4459

0
Comment actions Permalink

Just use define a system property -Didea.no.jdk.check=true

Modify bin\idea.lax

Change
lax.nl.current.vm=c:
java
jdk1.4.2
jre
bin
java.exe

Change
lax.nl.java.option.additional=-Xms16m -Xmx256m -XX:UseParNewGCUseConcMarkSweepGC -Didea.no.jdk.check=true -Didea.system.path="~
.IntelliJIdea
system" -Didea.config.path="~
.IntelliJIdea
config" -Didea.popup.weight=heavy

0
Comment actions Permalink

Wow, nice significant speed difference in the IDE! Well on my zipper
machine anyway.

Thanks
R

"Weicong Wang" <no_mail@jetbrains.com> wrote in message
news:10010598.1057181677317.JavaMail.itn@is.intellij.net...

Just use define a system property -Didea.no.jdk.check=true

>

Modify bin\idea.lax

>

Change
lax.nl.current.vm=c:
java
jdk1.4.2
jre
bin
java.exe

>

Change

>


lax.nl.java.option.additional=-Xms16m -Xmx256m -XX:UseParNewGCUseConcMarkS
weepGC -Didea.no.jdk.check=true -Didea.system.path="~
.IntelliJIdea
system
" -Didea.config.path="~
.IntelliJIdea
config" -Didea.popup.weight=heavy
>


0
Comment actions Permalink

Just use define a system property -Didea.no.jdk.check=true


Thanks a lot!
I am running b833 under 1.4.2. FileChooser is very fast.
It no more tries to read my floppy!

0
Comment actions Permalink


Yes, it's a very simple test that measures startup times. But as that's been one of the main selling points of jdk1.4.2 it's a bit dissapointing to see the startup performance is so much worse than 1.3.1. I appreciate seeing correct icons for files and having a file chooser that fits in with the OS, but not at the cost of waiting 30 seconds.

I'm not a big user of 'Open File', but would appreciate it if it appeared quickly the first time I opened it. This can quite easily be accomplished by constructing a JFileChooser in a background thread while IntelliJ starts up because, as you say, the VM caches quite well.

0
Comment actions Permalink

But it does not take 30 seconds the first time. It only takes 0.5 seconds (on build 833 with jdk1.4.2 PIII 1GHz
with some network mounted disks).

0
Comment actions Permalink

It's nice that it's so quick for you, but on my machine with my network drivers it does not run that quickly. There's at least a five-fold slowdown between 1.3.1 and 1.4.2, and it's often 30 times slower. I should get a faster response than you if it was just down to processor power, but I don't; my experience is that 1.4.x does not play well.





0
Comment actions Permalink

Just use define a system property
-Didea.no.jdk.check=true

Modify bin\idea.lax

Change

lax.nl.current.vm=c:
java
jdk1.4.2
jre
bin
java.
xe

Change
lax.nl.java.option.additional=-Xms16m -Xmx256m
m -XX:UseParNewGCUseConcMarkSweepGC
-Didea.no.jdk.check=true
-Didea.system.path="~
.IntelliJIdea
system"
-Didea.config.path="~
.IntelliJIdea
config"
-Didea.popup.weight=heavy


Did that with IDEA 3.0.4. When opening a project it threw some unknown error and the toolbar items 1:project, 7:structure 6:TODO 2:Commander where nowhere to be found. Needless to say I had to switch back to bundled jre.

P.S.
I also tried to replace bundled jvm's files with 1.4.2 ones where there were differences. Same result.

0
Comment actions Permalink

yes, i lost the project and other toolbars also when opening up my most recent project under 1.4.2. just delete the contents of caches and restart, that helped me - its worth doing so for the massive speed boost in the filechooser (its fast).

0
Comment actions Permalink

How did you manage to run Aurora (or IDEA 3.0) on jdk 1.3.1?

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"




0
Comment actions Permalink

Actually it was like this before, but we started getting a lot of bugreports caused by using JDKs other, than recommended by us.
That's why the check was introduced and we started to bundle the "right" JRE together with IDEA..

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"



0
Comment actions Permalink

BTW, I feel that Aurora is less memory hungry compared with Ariadna,
especially with the new Optimization process.


Well, this depends on concrete build. Some of them are less hungry and some of them are compared. We are constantly working on
decreasing memory usage, but the final effects will be visible before the release.

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"



0
Comment actions Permalink

That did the trick for me also. Only thing now is that the Ant build view has black dots the size of 'o' instead of the text that shows what is happening. It is working fine though. File chooser is also faster. What a relief! It took anything between 5 to 30 secs to open file chooser...

Jari

0
Comment actions Permalink

I've been using 706 with JDK 1.4.2 for a day or so. So far so good except
ant builds fail with "compiler not found" errors which can be worked around
by choosing custom JVM rather than Idea's one in ant options


"Hezekiel" <tilaus@almasoftware.com> wrote in message
news:30732921.1057228367167.JavaMail.itn@is.intellij.net...

Just use define a system property
-Didea.no.jdk.check=true

>

Modify bin\idea.lax

>

Change

>

lax.nl.current.vm=c:
java
jdk1.4.2
jre
bin
java.
xe

>

Change
lax.nl.java.option.additional=-Xms16m -Xmx256m
m -XX:UseParNewGCUseConcMarkSweepGC
-Didea.no.jdk.check=true
-Didea.system.path="~
.IntelliJIdea
system"
-Didea.config.path="~
.IntelliJIdea
config"
-Didea.popup.weight=heavy

>

Did that with IDEA 3.0.4. When opening a project it threw some unknown

error and the toolbar items 1:project, 7:structure 6:TODO 2:Commander where
nowhere to be found. Needless to say I had to switch back to bundled jre.
>

P.S.
I also tried to replace bundled jvm's files with 1.4.2 ones where there

were differences. Same result.


0
Comment actions Permalink

How did you manage to run Aurora (or IDEA 3.0) on jdk
1.3.1?


I was using 1.3.1 to check the speed of JFileChooser, not to run Aurora.


--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"




0
Comment actions Permalink

Have your problems been solved. I too get file chooser times in the regions you have described and it's driving me insane. I have tried plugging in 1.4.2 but have not had any improvements. Don't have any problems with other java apps so this must be and idea issue in some way shape or form.



Re: Will Aurora 3.0.5 have JDK 1.4.2 please? Posted: Jul 2, 2003 4:08 PM Reply

I have the same problem. The reason is it scan floppy drive (empty) every
time I double-click to change directory

"Vladimir Kondratyev" <vova(at)intellij.net> wrote in message
news:bdur8c$i43$1(at)is.intellij.net...

Trevor wrote:

click file open icon - 45 s
click Look in pull down list - 15 s
open my work folder in file chooser - 25 s
configure libs - add - 22 s

0

Please sign in to leave a comment.