Garbage Collector
Get flash to fully experience Pearltrees
Oracle acquired Sun in 2010, and since that time Oracle's hardware and software engineers have worked side-by-side to build fully integrated systems and optimized solutions designed to achieve performance levels that are unmatched in the industry. Early examples include the Oracle Exadata Database Machine X2-8 , and the first Oracle Exalogic Elastic Cloud , both introduced in late 2010. During 2011, Oracle introduced the SPARC SuperCluster T4-4 , a general-purpose, engineered system with Oracle Solaris that delivered record-breaking performance on a series of enterprise benchmarks. Oracle's SPARC-based systems are some of the most scalable, reliable, and secure products available today. Sun's prized software portfolio has continued to develop as well, with new releases of Oracle Solaris , MySQL , and the recent introduction of Java 7 . Oracle invests in innovation by designing hardware and software systems that are engineered to work together.
BigAdmin Submitted Article: Understanding Concurrent Mark Sweep Garbage Collector Logs
Performance Tuning Garbage Collection in Java
This document is a summary or outline of Sun's document: Tuning Garbage collection with the 1.4.2 Hotspot JVM located here: http://java.sun.com/docs/hotspot/gc1.4.2/Garbage Collection: ConcMarkSweep vs. RMI | Webapper Blog
Abstract Use of the ConcMarkSweep garbage collector for the “tenured” generation is undesirable when RMI (Remote Method Invocation) garbage collection is occurring. Introduction
Turbo-charging Java HotSpot Virtual Machine, v1.4.x to Improve the Performance and Scalability of Application Servers
This paper describes the requirements of a Telecommunication (Telco) application server written in the Java programming language, and how those requirements might influence Java virtual machine (JVM 1 ) design. Most of the discussion is not limited to Telco alone, but applies to the enterprise as well. The paper: Finally, the paper includes a case study of a Session Initiation Protocol (SIP) server that demonstrates significant performance gains from using these new collectors and other tuning techniques described.
This document describes the behavior of the Java( tm ) HotSpot ( tm ) virtual machine. This behavior is not part of the VM specification, however, and is subject to change in future releases. Moreover the behavior described here is generic behavior and will not apply to the execution of all Java applications. How is the generational collector implemented in HotSpot(tm)?
Garbage Collection - Frequently Asked Questions
Use the concurrent low pause collector if your application would benefit from shorter garbage collector pauses and can afford to share processor resources with the garbage collector when the application is running. Typically applications which have a relatively large set of long-lived data (a large tenured generation), and run on machines with two or more processors tend to benefit from the use of this collector. However, this collector should be considered for any application with a low pause time requirement.
