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 |

Our valued sponsors who help make this site possible
New Relic: Try free w/ production profiling and get a free shirt! 

ManageEngine's Site24x7: End-to-End analysis on Java EE web transactions. Sign up for FREE! 

AppDynamics: Get complete browser to backend visibility. Monitor Now! 

News August 26, 2003

Chart Java Jitter with jHiccup
Monitor and identify pauses in your Java apps. Download now

Why is my application so slow?
Learn 3 ways to detect Java Application Performance Trends

JProfiler
Get rid of your performance problems and memory leaks!


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

See Your Message Here
You could have your tool advertised here, to be seen by thousands of potential customers

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:


New Relic
New Relic: Try free w/ production profiling and get a free shirt!

ManageEngine
ManageEngine's Site24x7: End-to-End analysis on Java EE web transactions. Sign up for FREE!

AppDynamics
AppDynamics: Get complete browser to backend visibility. Monitor Now!


Chart Java Jitter with jHiccup
Monitor and identify pauses in your Java apps. Download now

Why is my application so slow?
Learn 3 ways to detect Java Application Performance Trends

JProfiler
Get rid of your performance problems and memory leaks!


Back to newsletter 033 contents

I had a bit of a rant about the difference between being able to use a profiler and being able to performance tune an application. It came from the fact that every site I have ever been to in the last five years has owned a profiler, but still had performance problems.

Of course, I have what is known as "experience bias". Doctor's don't tend to see healthy people visiting their offices to get a diagnosis, so consequently they can have a distorted view of how healthy the overall population is. People who have just lost their job and are finding it difficult to find another feel that the economy is not doing well, even when it is. The same type of "experience bias" afflicts me: I will not be asked to come and performance tune a project that is doing fine. But that doesn't change the fact that all those projects that I do get to already have a profiler. And they know how to use it, having almost always sent at least one developer to attend the vendor course. In fact I'm often presented with several saved profiles to look at, as one of my first tasks!

Knowing how to use the profiler doesn't seem to be quite enough. Knowing how to performance tune is a wider skill, and it is one that we here at JavaPerformanceTuning.com give you the ability to perform whether that be by using our 3,000+ tips; or by reading our recommended book "Java Performance Tuning, 2nd ed" with it's 300 tuning techniques; or by our excellent Java Performance Training Courses; or even just by keeping up to date by reading our monthly newsletters with their comprehensive focus on Java performance;

A note from this newsletter's sponsor

JProbe helps developers understand precisely what is causing
problems in Java applications - right down to the offending
line of source code. Download a free evaluation of JProbe today.

This month we've selected a diverse and interesting set of articles to extract tips from. GUIs (wait cursors); J2EE (session scopes, messaging EJBs, app-server tuning); performance management; several JVM and core classes tips; and a look forward to several of the classes due to become available with 1.5 and it's inclusion of the java.util.concurrent package.

In addition, we have our usual sections. Kirk's roundup covers micro-benchmarks, adaptive JVM advantages, McCabe Complexity, the shelf-life of tips, obfuscation, and more. Our interview this month is with Steven Haines, J2EE architect for Quest Software, who shares with us his expert knowledge of current performance issues. Our question of the month asks about the effectiveness of pooling objects. Javva The Hutt details how he set up his constant response-time production server; and, of course, we have many new performance tips extracted in concise form.

News

Tools

A note from this newsletter's sponsor

Brought to you by Veritas: Download your
"Risks of Performance Problems in J2EE Projects"
White Paper written by Jack Shirazi, Director of JavaPerformanceTuning.com

Recent Articles

Older Articles

Jack Shirazi


Back to newsletter 033 contents


Last Updated: 2014-10-03
Copyright © 2000-2014 Fasterj.com. All Rights Reserved.
All trademarks and registered trademarks appearing on JavaPerformanceTuning.com are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries. JavaPerformanceTuning.com is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.
URL: http://www.JavaPerformanceTuning.com/news/news033.shtml
RSS Feed: http://www.JavaPerformanceTuning.com/newsletters.rss
Trouble with this page? Please contact us