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 June 2017

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

The 80/20 rule of thumb suggests that 80% of your code doesn't really need to be particularly efficient, but it's not always clear to developers whether the component they are developing falls into that 80%, or if they need to make extra effort on the performance and memory for any particular component. I gave guidelines for this in my Devoxx talk (the recorded talk now available at this link), where I spoke about 3 axes of performance: concurrency, data size and responsiveness.

A note from this newsletter's sponsor

New Relic - Try New Relic today and get your free Data Nerd shirt!
Free SaaS APMto monitor, troubleshoot, and tune apps
running on Websphere, Weblogic, Tomcat, Jetty, JBoss, Solr, Resin

These three axes are particularly useful for characterising the need for performance and memory efficiency during development. For the most part, following good coding practices will give you components that are likely to achieve your performance goals, but using these axes tells you when you need to go beyond good coding practices. In my talk and in the slides I give some guidelines for when you need to think about whether you need to make a special effort for your component.

Library developers think a little differently, they tend to take the defensive stance that anything they make needs to be as fast and as small as possible, which may be a reasonable point of view, but makes development very expensive. Library developers also depend on microbenchmarks quite extensively to achieve "as fast and as small as possible" - the 3 axes of performance are less useful for library developers, but still apply. In the next few newsletters I'll focus a little more on each axis.

Now on to our usual links to articles, tools, news, talks, blogs. And if you need the tips from this month's articles and talks, as ever they are extracted into this month's tips page.


Java performance tuning related news.


Java performance tuning related tools.

A note from this newsletter's sponsor : Deep dive Application Performance Monitoring
Fix performance issues with Java, .NET and Ruby platforms
Monitor app instance at $12/Month. 30-day free trial. Sign Up!


Jack Shirazi

Back to newsletter 199 contents

Last Updated: 2024-03-29
Copyright © 2000-2024 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