[ jEdit-devel ] [ jedit-Bugs-1557986 ] 4.3pre6 very slow on JDK 1.6 beta2

[SourceForge.net <no...@so...>]

Bugs item #1557986, was opened at 2006-09-13 17:34
Message generated for change (Comment added) made by kpouer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1557986&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Brian Pontarelli (brokenwren)
Assigned to: Nobody/Anonymous (nobody)
Summary: 4.3pre6 very slow on JDK 1.6 beta2

Initial Comment:
Another things I've noticed is that JEdit 4.3pre6
running under JDK 1.6 beta2 is very slow. I'm not sure
what is causing the slow down, but all other
applications I've run on JDK 1.6 beta2 have shown a
very good performace increase, except JEdit.

----------------------------------------------------------------------

>Comment By: Matthieu Casanova (kpouer)
Date: 2006-12-13 16:28

Message:
Logged In: YES 
user_id=285591
Originator: NO

too bad, my little test with beanshell is still true with JDK 1.6 final.
Still very slow against JDK 1.5 ...

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2006-10-08 19:02

Message:
Logged In: YES 
user_id=935841

try moving out the startup/getGraphicsEnvironment.bsh and
see if that causes a defer of the lockup, from startup to
later when you bring up your first context menu.

Also, please describe your specific hardware -  could it be
related to either your graphics driver/card/settings, or the
hyperthreading/multiprocessor settings? 


----------------------------------------------------------------------

Comment By: jfd (jurgenfd)
Date: 2006-09-27 18:20

Message:
Logged In: YES 
user_id=1380111

Perhaps related for Java 1.5.0_06 and jedit 4.3pre6:
Startup on Windows hangs for 13 seconds at ~80% done and
then works fantastic. Annoying. Rebooting the machine fixed
it but it came back. Could it be an older jedit install
lying around using the same server?

----------------------------------------------------------------------

Comment By: Matthieu Casanova (kpouer)
Date: 2006-09-25 17:45

Message:
Logged In: YES 
user_id=285591

I tried too with -server command but still no problem here
with JDK 1.6.0 beta 2 on Windows XP SP2

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2006-09-22 22:16

Message:
Logged In: YES 
user_id=935841

I can not reproduce this on my system, and I'm also using
linux, KDE, and jdk 1.6beta2. I ran the test you sent and
got 110 ms under jdk 1.6beta2.



----------------------------------------------------------------------

Comment By: Brian Pontarelli (brokenwren)
Date: 2006-09-22 21:42

Message:
Logged In: YES 
user_id=1541332

Tried -client and still has the same problem. It might be
worse actually. One of the most horrific issues is that when
JEdit gets focus it completely pins the CPU for an instant,
locking up even Linux momentarily. Real pain.

----------------------------------------------------------------------

Comment By: Dale Anson (daleanson)
Date: 2006-09-22 18:59

Message:
Logged In: YES 
user_id=187628

Have you tried using -client rather than -server?

----------------------------------------------------------------------

Comment By: Brian Pontarelli (brokenwren)
Date: 2006-09-22 18:37

Message:
Logged In: YES 
user_id=1541332

No, I'm using this command line:

/opt/programs/jdk1.6.0/jre/bin/java -server -mx128m
-classpath /opt/programs/jedit/4.3pre6/jedit.jar
org.gjt.sp.jedit.jEdit

which is what JEdit ships with. Perhaps the server VM flag
is making JDK 1.6 mad. I'll try a few other tweaks and see
if I can get some more responsiveness. Oh and I'm using Linux.

----------------------------------------------------------------------

Comment By: Matthieu Casanova (kpouer)
Date: 2006-09-21 15:48

Message:
Logged In: YES 
user_id=285591

Hi, are you launching jEdit in debug mode ?
I just made some tests and it seems that debug on JDK 1.6
beta 2 is slower than JDK 1.5.

I tried to evaluate the following beanshell code in jEdit

long start = System.currentTimeMillis();
int a = 0;

for (int i = 0;i<10000;i++)
{
a = i * 2;
}
long end = System.currentTimeMillis();
System.out.println(end - start);

here are my results :
1.5 debug activated : 78 ms
1.6 no debug : 78 ms
1.6 debug activated : 1200 ms !!!!!

so debugging with 1.6 is very slow (with Windows JVM, I did
not test another one)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1557986&group_id=588