When you set out to optimize the performance of a multi-user application, a natural focus is removing or minimizing application contentions. For Java applications, there is one common source of contention: garbage collection (GC). This article explains in detail how GC affects application execution, and presents a formula you can use to predict the extent to which GC in your system will affect your applications. It also provides recommendations on what you can do if GC is the principle source for performance deterioration in your system, and steps you can take toward memory-conscious programming to help you on your way toward an optimally performing system.
Rudolf Meier
Rudolf Meier began his IT experience in data acquisition, analysis, and simulation of physics experiments at accelerator labs around the globe. He joined the SAP Performance, Data Management and Scalability team in 2004. In addition to working on ABAP performance topics, he also focuses on the performance of new UI technologies in the Java world. Rudolf received his Ph.D. in Experimental Physics from the University of Karlsruhe in 1993, and he is a private lecturer at the University of Tübingen, Germany.
You may contact the author at rudolf.meier@sap.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.
Premium
