How can I improve the performance of JBuilder 3.5?

NOTE: The following performance tip is NOT supported by Inprise/Borland Developer Support. You will not receive support for problems encountered with JBuilder after implementing these steps. You use this FAQ at your own risk.

With the release of JDK 1.3 on Windows, Sun also included a new version of their HotSpot client Virtual Machine. This new HotSpot client appears to be compatible with JDK 1.2 and features improved performance including better garbage collection. This FAQ will outline to steps to plug the new HotSpot client into the JDK that is installed with JBuilder 3.5 on Windows. It is possible that similar steps may be used on other operating systems but this has not been tested.

1. First, install JDK 1.3.
2. Look for a directory under "jdk1.3/jre/bin" (or its equivalent) called "hotspot".
3. Copy this directory to the equivalent directory in JDK 1.2.2 that was installed with JBuilder. For example copy "C:\jdk1.3:\jre:\bin:\hotspot" to "C::\jbuilder35:\jdk1.2.2:\jre:\bin".

That is all that's needed. The VM that runs JBuilder will see the HotSpot directory and use the new Client VM.

Note that when you debug your programs in JBuilder 3.5 after installing HotSpot, the performance may suffer. To fix this you need to add a VM parameter to your Project Properties that will turn off HotSpot for when you debug.

1. Open a project.
2. Open the Project Properties.
3. Slecect the "Run" tab.
4. In the VM Parameters box add "-classic".

This change forces the VM that runs your program to use the "classic" client Virtual Machine instead of HotSpot.