Java Performance Tuning

Java(TM) - see bottom of page

|home |services |training |newsletter |tuning tips |tool reports |articles |resources |about us |site map |contact us |
Tools: | GC log analysers| Multi-tenancy tools| Books| SizeOf| Thread analysers| Heap dump analysers|

Our valued sponsors who help make this site possible
JProfiler: Get rid of your performance problems and memory leaks! 

Training online: Concurrency, Threading, GC, Advanced Java and more ... 

News September 2021

Get rid of your performance problems and memory leaks!

Modern Garbage Collection Tuning
Shows tuning flow chart for GC tuning

Java Performance Training Courses
COURSES AVAILABLE NOW. We can provide training courses to handle all your Java performance needs

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:

Training online
Threading Essentials course

Get rid of your performance problems and memory leaks!

Back to newsletter 250 contents

No matter how well implemented your application may be, you can't prevent a JVM dying unexpectedly from causes outside your application. The usual solution to this is to provide your application running on more than one JVMs, fronted by load distributors - a cluster. This in turn may be insufficient if you need high availability, because the whole cluster could die. The usual solution to this is to run in more than one region.

Deciding how far you go in keeping your application available, requires you to make decisions. Is the JVM deployed active-active in one region? That has implications for how caches are maintained. Active/active in multiple regions? That has implications in syncing data across regions. Maybe you can go with an active/hot-standby setup. Now you need to think about how failover happens and whether any data or requests would be lost. Maybe an active/passive setup works? Then you need to think about scaling to handle the request load as you failover. There's also active/quick-deploy-and-start as an option. Is your system capable of deploying quickly to a new datacentre? What if no existing infrastructure is already present?

There are a host of options and decisions to make, each with consequences to your design, architecture and implementations. Just make sure you decide on the availability you want to provide and ensure that you can attain it. Not thinking about this is a recipe for failure.

Now on to all the usual newsletter list of links, tips, tools, news and articles, and as usual I've extracted all the tips into this month's tips page .

A note from this newsletter's sponsor

Get rid of your performance problems and memory leaks!


Java performance tuning related news


Java performance tuning related tools


Jack Shirazi

Back to newsletter 250 contents

Last Updated: 2022-06-29
Copyright © 2000-2022 All Rights Reserved.
All trademarks and registered trademarks appearing on are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries. is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.
RSS Feed:
Trouble with this page? Please contact us