• 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