JRockit

As every one know java is one of the most powerfull programming tools in this world, java application can be run on many platform (create once run every where). Every java aplication need JVM (Java Virtual Machine), without JVM java aplication cannot be run.

Oracle build with java technology in all core. This why oracle can be installed in other Operating System. As Java aplication Oracle need a virtual machine, but now Oracle have they own Virtual machine and they have name We must be wondering what is the different JVM with JRockit?

As we know JVM (SUN Microsystem) have a high memory used, Oracle try to break this with JRockit problem as the first JVM uniquely optimized for the Intel platform, enabling Java applications to run with increased reliability and performance on lower cost, standard-based platforms. Unlike other JVMs, BEA JRockit is designed to power demanding server-side Java
applications-delivering superior performance, manageability, and reliability for enterprise applications.

According to industry benchmarks, BEA JRockit leads in performance over other published RISC-based benchmark results. Today, BEA customers are seeing significant performance increases—some exceeding 70 percent—and reductions in hardware costs of as much as 50 percent. BEA JRockit on Intel architectures enables enterprises to achieve ROI at all levels of the infrastructure stack because of its:

• High performance, which accelerates application execution and implements JVM functionality efficiently

• Reliability, which handles the heaviest loads without failing

• Manageability, which delivers real-time server and resource visibility through an independent management console

• Scalability, which meets rapidly growing numbers of users without disruption

BEA JRockit builds on state-of-the-art optimization technology to achieve the highest performance possible on Intel hardware. The system uses an adaptive optimizing compiler to accelerate bytecode execution. Internal functions like thread synchronization, object allocation, array copying, and file/network communications are streamlined for speed—continually adapting to not only the Java application above, but also the operating system and server hardware below.

Optimized Code Generation

BEA JRockit monitors applications continuously and uses the application’s ongoing characteristics to adapt and upgrade performance. The software JIT compiles all methods it encounters during startup, continuously optimizing application code during runtime to improve performance.

A background bottleneck detector collects runtime statistics to detect bottlenecks caused by frequently executed methods. Then the system’s optimization manager aggressively optimizes these methods even as the program is running to deliver on-the-spot improvements.

Seamless Garbage Collection

BEA JRockit virtually eliminates the pauses and operational disruption that garbage collection often causes. The software supports four garbage collection methods to meet the requirements of different types of applications and environments:

• The parallel collector utilizes all CPUs on a multiprocessor system to quickly clear out all dead objects. While the use of this collector results in periodic application pauses, it also delivers the highest possible application throughput.

• Generational concurrent is a hybrid collector that works simultaneously in the background along with application threads. By allocating all new objects in a nursery that is typically less than 25% of the entire heap, and periodically pausing the application only to clear out this nursery, this collector delivers the smallest possible pause times on both single-processor and multi-processor systems.

• Single-spaced concurrent is a non-disruptive collector that runs concurrently with the application threads by operating simultaneuously on a subset of multi-processor system CPUs. This model allocates objects in a single large heap, which periodically results in the collector pausing to synchronize the application threads to obtain an accurate picture of live objects.

• Generational stop’n'copy is a standard two-generational collecting method that keeps all newly allocated objects in a special nursery. Objects are moved from this area to the older copying space when they have survived for a certain amount of time. This model is best used during application debugging.

High Visibility Management

BEA JRockit’s simple yet powerful management console opens up real-time information about server behavior and resource availability and proactively diagnoses problems to avoid downtime. This gives system administrators unique control over the deployment and management of commercial Java applications.

The management console lets you monitor CPU and memory utilization and make configuration changes to avoid application downtime. Administrators can monitor the operating characteristics of the JVM and the Java applications and receive automatic notification of changes as they occur.

Armed with this information, administrators can identify performance bottlenecks to adjust operating and environmental parameters for cleaner performance and availability.

BEA JRockit also supports both JVMDI and JVMPI to enable developers to use third-party debugging and profiling tools, and offers integration with leading third party application management tools.