JProfiler Get rid of your performance problems and memory leaks! Modern Garbage Collection Tuning 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! Enter email: JProfiler Get rid of your performance problems and memory leaks!

• 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
• The IllegalAccessException
• The ClassNotFoundException
• 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
• Multi-threading code
• 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
• Avoiding locks
• Understanding reference types
• Avoiding long pauses by the garbage collector
• Just-in-time compilation
• Detecting deadlocks
• 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
• Lazy initialization
• Speeding up the hardware

All cartoons are by our cartoonist, "profiler". "profiler" can contacted be via our contact page

Other cartoons by profiler:

• Unix commands can have unforeseen side effects

And cartoon listing sites that recognize profiler's cartoon genius:

• AA Cartoon Art