Save money with Jelastic’s new optimised Garbage Collector Agent
A few short months ago we explained how to experiment with custom JVM Garbage Collector settings on our Jelastic PaaS.
The fantastic development team behind Jelastic just announced that they too were hard at work experimenting with the GC, and as a result they’ve introduced new default GC settings to help to provide optimum performance right out of the box for all of your Java applications.
New default Garbage Collector settings
Prior to this update, Jelastic used the Serial GC by default if the Cloudlet Scaling Limit was set at or below 1GB (8 cloudlets), and the G1 GC by default if the Cloudlet Scaling Limit was set above 1GB.
How to Tune the Garbage Collector in Tomcat
The guys at PayPal recently switched away from Java, citing (perhaps false/questionable ?) performance gains. One important, but easily overlooked, way to keep your Java app performing at its best is to make sure that the JVM is well tuned to your needs – that includes taming the Garbage Collector.
If Java had true garbage collection, most programs would delete themselves upon execution.
– Robert Sewell
Java’s Garbage Collector does an important job, and if you tune it properly, you can prevent memory intensive programs from freezing your system. It’s easy to assume that if you know how to develop large programs and applications, you probably already know how the Garbage Collection process works. Ergo if you choose the right Garbage Collector algorithm, it means you totally understand the features of the program you have developed.
If you’re not quite sure how the whole process works, we’ll try to summarise the most important aspects for you.
Meet the Garbage Collector, it will save your day!
You’ve just developed a large application, and you couldn’t be more excited! But, as this application runs, it creates objects; as it continues to run, many of these objects are no longer required and they cause your program to run out of memory for no apparent reason.