Tutorial Addendum on JVM - JRockit JVM 8.0
| |
Test 6: Active LongSleep with HotSpot
For allegory purposes, I launched LongSleep with HotSpot JVM:
localj2sdk1.4.1_01injava LongSleep
Chargeless memory: 1781480
Total memory: 2031616
On the Windows Assignment Manager:
Before active LongWhile:
Achievement tab: CPU: 1%, MEM: 133052K
Once LongSleep started:
Achievement tab: CPU: 1%, MEM: 141424K
Processes tab - java: CPU: 0%, MEM: 4716K
10 account later: about the same.
Results looked ok.
Test 7: Active LongSleep with JRockit additional Management
Now, aback to JRockit, but with Administration advantage angry on this time:
localeajrockit80_141_32injava -Xmanagement LongSleep
[JRockit] Administration Server started on anchorage 7090.
Chargeless memory: 66912936
Total memory: 77594624
On the Windows Assignment Manager:
Before active LongWhile:
Achievement tab: CPU: 1%, MEM: 132032K
Once LongWhile started:
Achievement tab: CPU: 1%, MEM: 233220K
Processes tab - java: CPU: 0%, MEM: 12852K
10 account later: about the same.
Results looked ok too.
Test 8: Active LongSleep and JRockit Administration Animate Client
In this final test, I wish to run JRockit administration animate client, connecting
to my LongSleep active beneath JRockit JVM. So I started LongSleep first, then
launched the administration animate applicant program:
cd localeajrockit80_141_32consoleclient
....injava -jar ManagementConsole.jar
The applicant program started ok. I had no problem abutting the applicant program
to the animate server that was active with my LongWhile. The affiliation was
stable this time, but there was a altered problem, see my annal bellow:
On Windows Assignment Administrator - Afore active LongWhile:
Achievement tab: CPU: 1%, MEM: 132032K
On Windows Assignment Administrator - Already LongWhile started:
Achievement tab: CPU: 1%, MEM: 211088K
Processes tab - java: CPU: 0%, MEM: 12872K
On Windows Assignment Administrator - Already Administration Animate Applicant started:
Achievement tab: CPU: 24-35%, MEM: 358072K
Processes tab - java: CPU: 4%, MEM: 19520K - LongSleep
Processes tab - java: CPU: 21-31%, MEM: 116452K - Animate Client
4 account later:
Achievement tab: CPU: 24-35%, MEM: 358692K
Processes tab - java: CPU: 4%, MEM: 22320K - LongSleep
Processes tab - java: CPU: 21-31%, MEM: 129128K - Animate Client
4 account later:
Achievement tab: CPU: 24-35%, MEM: 358588K
Processes tab - java: CPU: 4%, MEM: 26312K - LongSleep
Processes tab - java: CPU: 21-31%, MEM: 129296K - Animate Client
10 account later:
Windows comatose with chat box saying:
"winlogon.exe - Appliance Error"
A brace of absorbing things to be acclaimed here:
- I again the test, and got agnate results.
- The blast seems to be accompanying to my awning saver, which was set to the Windows
logon chat box. I assumption I could about-face off my awning saver to abstain this crash.
- There was a apathetic access of anamnesis usages on both java instances: LongSleep
and Animate Client.
- The CPU acceptance was aquiver during the test. My assumption was that
the animate applicant program was affairs advice out of the animate server with
a anchored sampling interval.
On the anamnesis tab of the animate applicant program, I aswell noticed that the "used mem"
number was traveling up, while the "free mem" amount was traveling down. At one time, I recorded
the afterward numbers:
ocillation is espected because of sampling...
acclimated abundance 11139, acclimated mem: 295516
chargeless abundance 64620, chargeless mem: 226628
total abundance 75776, absolute mem: 522467
|
console, longsleep, processes, performance, jrockit, client, running, started, memory, management, windows, longwhile, later, minutes, manager, program, results, server, , tab cpu, performance tab, java cpu, tab java, processes tab, console client, task manager, windows task, minutes later, management console, client program, started performance, running longsleep, 35% mem, longsleep processes, 31% mem, longsleep with, manager before, longwhile performance, running longwhile, jrockit management, jrockit jvm, windows task manager, console client program, management console client, running longwhile performance, manager before running, task manager before, console client4 minutes, client4 minutes later, minutes later performance, task manager once, longwhile started performance, minutes later about, running longsleep with, jrockit management console, |
Text link code :
Hyper link code:
Also see ...
Let s use the afterward simple program to see how the Administration Animate works: /** * LongWhile.java * Absorb (c) 2002 by Dr. Yang */class LongWhile { accessible changeless
OverviewGenerally, a JVM is using the afterward rules to administer memory: When a JVM is invoked to run an application, it will ask the operating arrangement
Output on JRockit JVM with Xms2m Xmx64m Having 0 MB and abacus 10 MB... Chargeless memory: 8717040Total memory: 19419136Having 10 MB and abacus 10 MB... Chargeless memory: 8698800p