Tutorial Addendum on JVM - JRockit JVM 8.0

Installing JRockit JVM 8.0

    

One of the JRockit developers saw my addendum on JRockit 7.0 on the Web, and appropriate

    

me to try JRockit 8.0. So I downloaded the appraisal adaptation of JRockit 8.0, and

    

did a brace of quick tests.

    

To try JRockit 8.0, I went to http://commerce.bea.com/showallversions.jsp?family=WLJR.

    

Then using my registered name and password, I got the download page.

    

There, I called WebLogic JRockit 8.0 SDK, then Microsoft Windows (32 bit).

    

At the end of download process, I got

    

jrockit-8.0-j2se1.4.1-win32.exe (35,864KB).

    

The accession action was beeline advanced by bifold beat on

    

the downloaded file. At the end, JRockit was installed at

    

localeaJRockit80_141_32.

    

To analysis the installation, I did the afterward in a command window:

    

 

    
localeaJRockit80_141_32injava -version

    
java adaptation "1.4.1_01"

    
Java(TM) 2 Runtime Environment, Accepted Copy (build 1.4.1_01)

    
BEA WebLogic JRockit(R) Basic Apparatus (build 8.0-1.4.1_01-win32-CROSIS

    
-20030124-1058, Built-in Threads, Generational Circumstantial Debris Collecto

    
r)

    

There seems to be a Java compiler Interface' onMouseOver="tip('infobox1')" onMouseOut="untip()" target='_parent'> compiler Interface' onMouseOver="tip('infobox2')" onMouseOut="untip()" target='_parent'> compiler Interface' onMouseOver="tip('infobox1')" onMouseOut="untip()" target='_parent'> compiler Interface' onMouseOver="tip('infobox2')" onMouseOut="untip()" target='_parent'> compiler interface chip in JRockit 8.0:

    

 

    
localeaJRockit80_141_32injavac AnyClass.java

    
error: cannot read: AnyClass.java

    
1 error

    

Another aberration in 8.0 is that the Administration Animate server advantage is changed:

    

 

    
localeajrockit80_141_32injava -version -Xmanagement

    
[JRockit] Administration Server started on anchorage 7090.

    
...

    

Testing with LongWhile.java

    

Here is my LongWhile.java I acclimated afore to analysis the antecedent adaptation of JRockit:

    

 

    
/**

    
 * LongWhile.java

    
 * Absorb (c) 2002 by Dr.  Yang

    
 */

    
class LongWhile {

    
   accessible changeless abandoned main(String[] a) {

    
      Runtime rt = Runtime.getRuntime();

    
      System.out.println(" Chargeless memory: " + rt.freeMemory());

    
      System.out.println("Total memory: " + rt.totalMemory());

    
      while (true);

    
   }

    
}

    

Test 1: Active LongWhile with JRockit

    

I aggregate LongWhile with the compiler Interface' onMouseOver="tip('infobox1')" onMouseOut="untip()" target='_parent'> compiler Interface' onMouseOver="tip('infobox2')" onMouseOut="untip()" target='_parent'> compiler Interface' onMouseOver="tip('infobox1')" onMouseOut="untip()" target='_parent'> compiler Interface' onMouseOver="tip('infobox2')" onMouseOut="untip()" target='_parent'> compiler command interface provided by JRockit, then

    

launched it with JRockit JVM:

    

 

    
localeaJRockit80_141_32injava LongWhile

    
 Chargeless memory: 66936968

    
Total memory: 77594624

    

On the Windows Assignment Manager:

    

 

    
Before active LongWhile:

    
   Achievement tab:      CPU:   1%, MEM: 132032K

    
Once LongWhile started:

    
   Achievement tab:      CPU: 100%, MEM: 230468K

    
   Processes tab - java: CPU:  99%, MEM:  10740K

    
10 account later: about the same.

    

So, aggregate looked normal. But one absorbing breadth was that the anamnesis usages

    

reported by JRockit JVM and Windows Assignment Administrator were actual different: 77594K vs. 10740K.

    

Test 2: Active LongWhile with HotSpot

    

In adjustment to analyze with HotSpot, I again aloft analysis with J2SDK 1.4.1_01:

    

 

    
localj2sdk1.4.1_01injava LongWhile

    
 Chargeless memory: 1782304

    
Total memory: 2031616	

    

On the Windows Assignment Manager:

    

 

    
Before active LongWhile:

    
   Achievement tab:      CPU:   1%, MEM: 132032K

    
Once LongWhile started:

    
   Achievement tab:      CPU: 100%, MEM: 140960K

    
   Processes tab - java: CPU:  99%, MEM:   4716K

    
10 account later: about the same.

    

Obviously, the anamnesis acceptance appear by HotSpot akin bigger with Windows Assignment Manager:

    

2031K vs. 4716K. The aberration actuality reflected the anamnesis acceptance of the JVM itself.