Resource
Certification Resource
Forum
![[Level:5]](http://www.vietnamesetestingboard.org/zbxe/modules/point/icons/default/5.gif "Point:930point (54%), Level:5/30"){kind=icon}
nithyasai
2011.11.24 07:39:31
1795
Web Logic can be used for a wide variety of applications, from small applications to very large applications. In support of this diverse range of deployments, the Java Virtual Machine (JVM), in which Web Logic runs, provides multiple garbage collectors, each designed to satisfy different requirements. This is an important part of meeting the demands of both large and small applications. However, when we are dealing with applications that need high performance, we are burdened with the extra step of selecting the garbage collector that best meets the needs.
When does the choice of a garbage collector matter? For some applications, the answer is never. That is, the application can perform well in the presence of garbage collection with pauses of modest frequency and duration. However, this is not the case for a large class of applications, particularly those with large amounts of data, many threads and high transaction rates. Garbage collection is the single most important factor when tuning a JVM for long-running, server side applications. Improperly tuned garbage collectors or applications that create unnecessarily large numbers of objects can significantly affect the efficiency of the application. It is not uncommon to find that garbage collection consumes a significant amount of the overall processing time in a server-side Java application. Proper tuning of the garbage collector can significantly reduce the garbage collector’s processing time and, therefore, can significantly improve the application’s throughput.
When does the choice of a garbage collector matter? For some applications, the answer is never. That is, the application can perform well in the presence of garbage collection with pauses of modest frequency and duration. However, this is not the case for a large class of applications, particularly those with large amounts of data, many threads and high transaction rates. Garbage collection is the single most important factor when tuning a JVM for long-running, server side applications. Improperly tuned garbage collectors or applications that create unnecessarily large numbers of objects can significantly affect the efficiency of the application. It is not uncommon to find that garbage collection consumes a significant amount of the overall processing time in a server-side Java application. Proper tuning of the garbage collector can significantly reduce the garbage collector’s processing time and, therefore, can significantly improve the application’s throughput.
- Best,
- Practices,
- Optimizing,
- Web,
- Logic,
- Server,
- Performance,
- JVM,
- Tuning
![[Level:17]](http://www.vietnamesetestingboard.org/zbxe/modules/point/icons/default/17.gif "Point:8730point (5%), Level:17/30"){kind=icon}
![[Level:1]](http://www.vietnamesetestingboard.org/zbxe/modules/point/icons/default/1.gif "Point:110point (88%), Level:1/30"){kind=icon}
Service
New
Popular Documents
Popular Download
Weekly
Monthly
Yearly
Twitter
tag
Visitor
Thank you so much.