GC log analysers
Our valued sponsors who help make this site possible
JProfiler: Get rid of your performance problems and memory leaks!
Fasterj.com Site Map
Get rid of your performance problems and memory leaks!
Java Performance Tuning, 2nd ed
The classic and most comprehensive book on tuning Java
Java Performance Tuning Newsletter
Your source of Java performance news. Subscribe now!
Get rid of your performance problems and memory leaks!
Thread Analysers Tool Page
SizeOf Tools Page
Java Performance Related Books
Garbage Collector Log Analysers Tool Page
Multi-tenancy JVMs and Frameworks Tool Page
March 2014: Using SharedHashMap
June 2012: Jack Shirazi tells you what garbage collectors and garbage collector combinations are available from the Oracle Java 7 update 4 JVM
May 2012: Jack Shirazi tells you how to access the GC notifications newly available from Java 7 update 4
October 2008: Jack Shirazi details Five Lessons That Life Holds For Performance Tuning
August 2008: Kirk Pepperdine details the expected benefits of Sun's new "Garbage First (G1)" garbage collector.
July 2008: Kirk Pepperdine reviews Emily Halili's book "Apache JMeter".
May 2008: Kirk Pepperdine tells us about the performance session highspots at JavaOne: corestat, fork-join & how to load balance using dequeues, a lockless fully concurrent HashMap that scales to hundreds of cores, and the G1 garbage collector.
March 2008: Kirk Pepperdine interviews Dan Diephouse on XML performance
January 2008: Java Performance Review Of 2007. Jack Shirazi reviews the Java performance trends and newsworthy items from 2007.
December 2007: What people were looking for in Java performance in 2007. Using well over a million page views by over 100 000 people from our sites, we get an idea of what our readership were looking for in 2007. And to avoid suspense, "volatile" seems to have been flavor of the year.
November 2007: The Secret Life Of The Finalizer. Jack Shirazi looks into exactly what the JVM does when you create a finalizable object and then have it garbage collected. And it is surprisingly bizarre at times.
September 2007: Optimising Regular Expression Processing. Jack Shirazi looks at optimizing the performance of java.util.regex regular expressions.
July 2007: Cray Reminiscences: Kirk Pepperdine's attendence of AMD's performance talk at JavaOne produced a cascade of fascinating memories about Cray optimizations.
June 2007: Writing A Technical Book: Is It Worthwhile? Jack Shirazi, the author of the successful book 'Java Performance Tuning', discusses some basic considerations for you to mull over if you are ever thinking about writing your technical book."
May 2007: Su Doku Solving Efficiency: In this article Jack Shirazi considers how efficient the rules he uses for Su Doku solving are and, in the process, finds that he falls into the usual benchmarking traps. And he's surprised at how far simple rules get you.
April 2007: Kirk Pepperdine, interviews Ron Bodkin of Glassbox, Glassbox are the primary motivators for Glassbox the open source automated troubleshooting and monitoring agent for Java apps.
March 2007: The APM Score. Calculate your performance management score and see how much more there is to do. Here Jack Shirazi covers the details needed to make your performance management topnotch.
February 2007: Hotpatching A Java Application. How to fix arbitrary code-level problems in a running application without terminating that application. Here Jack Shirazi covers the basics of how to hotpatch a Java 6 application
Improve performance by reducing application space and time
Use the latest evolution of your JVM
Measure that your change actually fixes the bottleneck
Sizing the generations is the most important tuning option
More abstraction gives better performance ... eventually
Evolve performance by adopting industry best practices
Use priority queueing to prevent delays
Flattening objects can reduce garbage
Profilers often disagree with each other
Go for the easy performance targets first
The out of the box configuration is rarely optimal for performance
Slow garbage collection inspires the invention of multi-core processors
Measure service times to highlight slow servers
Where the application spends its time
Database connection pools can fix connection leaks
Use collections correctly
Synchronize to avoid race conditions
Faster startup from the disk sweet spot
Guard your log messages
Understanding Escape Analysis
Concurrency vs. Parallelism
Avoiding remote calls
Synchronizing methods can slow them down
A profiler profiling
Locks protecting single fields can often be replaced by making the field volatile
Understanding reference types
Avoiding long pauses by the garbage collector
Caching remote objects
Dumping heap on an out of memory error
Do not allocate memory during the main game loop
Choosing a different garbage collector
Eliminating common expressions
Reducing the size of collections
Adding RAM to the computer
Reducing the number of String objects
Increasing the size of the heap
Monitoring the server
Using state-of-the-art bottleneck identification tools
Clustering to reduce overheads
Reducing unnecessary communication overheads
Reading in parallel
Speeding up the hardware
Contacting Us and our info
Advertising at Fasterj.com
Last Updated: 2018-12-15
Copyright © 2007-2018 Fasterj.com. All Rights Reserved.
All trademarks and registered trademarks appearing on Fasterj.com are the property of their respective owners.
Trouble with this page?
Please contact us