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 December 2006

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 073 contents

Java 6 has been released just as we've finally moved our production systems to Java 5. And I see that a number of bugs fixed in Java 6 are being backported to the next Java 5 release - I'd love to say that this was because of my October newsletter, but in reality I'm sure that Sun planned to do this at some point - it's not really reasonable to expect all customers to leap to the Java 6 JVM anytime soon and so critical bugs needed to be backported.

A note from this newsletter's sponsor

Symantec i3 for J2EE helps you optimize application performance through
out the application life cycle. Its unique adaptive instrumentation
auto-adapts to application changes. Download an eBook on J2EE performance

I have a suggestion for Sun. Alternate bug fix and feature releases. I know this would be painful, but I'd really like to see the next 1.5 release holding only bug fixes, and no new features at all. Mixing new features with bug fixes in the same release just makes it too easy for new bugs to get into the release - I was previously stuck on 1.4.1 in production for far too long because each time we tested a move to 1.4.2, we hit a different critical bug that had been introduced in patch releases. I'd rather not have the same thing happen again.

Now on to our newsletter. First off, oops, we had the wrong devX link in last month's newsletter, the "Real-Time Tracking and Tuning for Busy Tomcat Servers" article is at and not the one we linked to. Javva the Hutt continues to tell us all about what he was doing while he was away. (For those of you who don't know Javva, or want a reminder, we've added a page for you to access all his old columns here.) And of course we have our other news, this months selected articles, tools, and our many new extracted performance tips.

A note from this newsletter's sponsor

Join the Battle Against Bad Java Code in Production
Effectively implement performance testing in development -
Read the Quest white paper - and get a JProbe® t-shirt!


Java performance tuning related news.


Java performance tuning related tools.

A note from this newsletter's sponsor

Wily Technology delivers what you need: Availability, Performance and Control
The most critical web applications in the world are managed by
software from Wily, the leader in enterprise application management


Jack Shirazi

Back to newsletter 073 contents

Last Updated: 2023-09-28
Copyright © 2000-2023 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