Re: JDEbug performance
Start your java application with a -classic option to disable HotSpot - then it runs smooth! What JVM are you running under? java -version java version 1.3.1_02 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_02-b02) Java HotSpot(TM) Client VM (build 1.3.1_02-b02, mixed mode) Runing on Windows 2000 Service pack 2 I am just setting -Djava.compiler=NONE That was also enough in the good old days :) This is from my 1.3.1_02 javadoc: The Java HotSpotTM Client VM The Java HotSpot Client VM is the default virtual machine. Its use of Java HotSpot technology gives it superior performance to that of the Classic VM. Unless special command-line options are used to invoke the Classic VM instead (see below), java will always launch an application to run on the Client VM. The Java 2 Classic VM The Java 2 Classic VM is essentially the same virtual machine implementation as in version 1.2 of the Java 2 SDK. It may be invoked by using the -classic command-line option, as in this example: java -classic MyApp The Java 2 Classic VM is included only in the Java 2 SDK. It is not included in the Java 2 Runtime Environment. The -classic option will not work with the Java 2 Runtime Environment. So, even the doc says: To disable HotSpot use -classic, AND it is only possible on the SDK. I also read at some point which I can't find again (nice proof, eh! :) that the JDK in 1.3 will ignore the -Djava.compiler=NONE instruction and still use HotSpot. A while ago I posted some fixes/suggestions for changes in JDE to ensure that debugged applications started from JDE ran in classic mode, but I do not know if these changes have made it into the codebase yet Do you have this documented anywhere? What was the subject line? Here is some trace of it. http://www.mail-archive.com/jde@sunsite.dk/msg02979.html Maybe it has been fixed - can't remember it. But this still holds: But the solution is to just start your java app externally from e.g. Ant or a simple commandline and then just attach to the JVM from JDebug. With hope Max
Re: JDEbug performance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Max Rydahl Andersen [EMAIL PROTECTED] writes: Start your java application with a -classic option to disable HotSpot - then it runs smooth! What JVM are you running under? java -version java version 1.3.1_02 Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_02-b02) Java HotSpot(TM) Client VM (build 1.3.1_02-b02, mixed mode) snip/ I also read at some point which I can't find again (nice proof, eh! :) that the JDK in 1.3 will ignore the -Djava.compiler=NONE instruction and still use HotSpot. Oh... that is good! :( You know... I was just going over some code... The -classic option did seem to speed things up. Of course this is totally anecdotal.. A while ago I posted some fixes/suggestions for changes in JDE to ensure that debugged applications started from JDE ran in classic mode, but I do not know if these changes have made it into the codebase yet Do you have this documented anywhere? What was the subject line? Here is some trace of it. http://www.mail-archive.com/jde@sunsite.dk/msg02979.html Maybe it has been fixed - can't remember it. But this still holds: But the solution is to just start your java app externally from e.g. Ant or a simple commandline and then just attach to the JVM from JDebug. snip/ Yes... doing that anyway... from Ant. Kevin - -- Kevin A. Burton ( [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] ) Location - San Francisco, CA, Cell - 415.595.9965 Jabber - [EMAIL PROTECTED], Web - http://relativity.yi.org/ They must have programmed it to get rid of the competition! You mean like Microsoft? Exactly! -- Simpsons -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt iD8DBQE8WlyrAwM6xb2dfE0RAsviAJ49UR3E4aI+bZouEaa5j+Dn9P8XVACff8Jq FGP6j0A3qBlHGUso7VCyKOY= =jKWI -END PGP SIGNATURE-
Re: JDEbug performance
Max Rydahl Andersen wrote: What if they phased it out altogether in the next sdk? The Java 2 Classic VM The Java 2 Classic VM is essentially the same virtual machine implementation as in version 1.2 of the Java 2 SDK. It may be invoked by using the -classic command-line option, as in this example: java -classic MyApp The Java 2 Classic VM is included only in the Java 2 SDK. It is not included in the Java 2 Runtime Environment. The -classic option will not work with the Java 2 Runtime Environment. Heather
JDEbug performance
I finally got fed up trying to debug servlet-type processes with println statements so I'm going debugger. I got jdb working okay but of course its interface is a little clunky, especially compared to a nice in-your-editor display. So I set up JDEbug and gave it a go. Right away I said yes! this rocks! but unfortunately the performance seems pretty awful compared to command-line jdb. Variable queries take ~30 seconds to come back; stepping from line to line is very slow as well. This all works as one might expect (i.e. quickly) in command-line jdb. I'm running on Win2000, using shared memory to attach to a running process. Is this known behavior for JDEbug? If not, any advice? (I haven't tried jdb under JDE yet but I'm about to.) Thanks! scott
JDEbug performance
I finally got fed up trying to debug servlet-type processes with println statements so I'm going debugger. I got jdb working okay but of course its interface is a little clunky, especially compared to a nice in-your-editor display. So I set up JDEbug and gave it a go. Right away I said yes! this rocks! but unfortunately the performance seems pretty awful compared to command-line jdb. Variable queries take ~30 seconds to come back; stepping from line to line is very slow as well. This all works as one might expect (i.e. quickly) in command-line jdb. I'm running on Win2000, using shared memory to attach to a running process. Is this known behavior for JDEbug? If not, any advice? (I haven't tried jdb under JDE yet but I'm about to.) Thanks! scott
Re: JDEbug performance
unny you should ask that as im just sitting doing the same thing - and I got an answer :) Start your java application with a -classic option to disable HotSpot - then it runs smooth! Huh... when I try -classic -Xdebug, I get: Exception in thread main java.lang.NoClassDefFoundError: sun/tools/agent/Agent Could not create the Java virtual machine. Running just -classic works, but adding the -Xdebug gives me the above barfage. scott
Re: JDEbug performance
Huh... when I try -classic -Xdebug, I get: Exception in thread main java.lang.NoClassDefFoundError: sun/tools/agent/Agent Could not create the Java virtual machine. Running just -classic works, but adding the -Xdebug gives me the above barfage. It should be the very first argument to java! This one works for me (running it via ant) jdk-1.3.1_02\jre\..\bin\java.exe -classic -Xrunjdwp:transport=dt_socket,addr ess=2112,server=y,suspend=y -Xdebug -Xnoagent -
Re: JDEbug performance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Scott Evans [EMAIL PROTECTED] writes: I finally got fed up trying to debug servlet-type processes with println statements so I'm going debugger. I think the killer combo could be: JDEBug/JPDA Tomcat class reloading Cactus unit testing ... I am going to play with that today. I wills send off a report :) I got jdb working okay but of course its interface is a little clunky, especially compared to a nice in-your-editor display. So I set up JDEbug and gave it a go. Right away I said yes! this rocks! but unfortunately the performance seems pretty awful compared to command-line jdb. It is also kind of quirky... you will see what I mean :) Variable queries take ~30 seconds to come back; stepping from line to line is very slow as well. This all works as one might expect (i.e. quickly) in command-line jdb. How are you running command-line in JDB? Are you using TCP or shared memory or in-VM??? I'm running on Win2000, using shared memory to attach to a running process. Is this known behavior for JDEbug? If not, any advice? snip/ Yes... it is kind of sluggish. Kevin - -- Kevin A. Burton ( [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] ) Location - San Francisco, CA, Cell - 415.595.9965 Jabber - [EMAIL PROTECTED], Web - http://relativity.yi.org/ Resistance is *not* futile! -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt iD8DBQE8WcDmAwM6xb2dfE0RAincAKCLMe/rNJRMVGyFzTMoexESGUsRBgCgyBfv clJ5OE8PbnUyRcOmwjbHruk= =I2Qu -END PGP SIGNATURE-
