Apache JMeter is an open source tool that can be used to measure the performance of Java applications. The JMeter can be used to test a wide range of Java applications like web, EJB, web services etc. I am not going to elaborate more on this, and you can get more information about this from the Apache JMeter website at http://jakarta.apache.org/jmeter/
The JMeter can also be extended, to create...
With the current stable JDK 6u7 it is not possible to generate heap dump on linux 64 bits. Looks like it was a bug, fixed on JDK 6 u10 RC. Read on for more details.
There is a very useful site at wikis.sun.com where you can have a better understanding of HotSpot Internals, maintained by HotSpot programmers, highly valuable.
You can see my presentation about Tools and Tips to Diagnose Performance Issues on-line or download it. It was great, because the room was almost full, people keep taking pictures, looks like the topic was interesting. Some people asked questions at the end, where I want to answer here, to a broad audience.
What are the available tools to read and understand heap and thread dump files ? How to detect a memory leak on Java applications ? How to detect thread contention issues ? Those are all question I want to answer and show some examples at Jazoon conference, along other tools and tips. My session is "Tools and Tips to Diagnose Performance Issues", scheduled to go on June, 24, 5:30pm.
Sometimes small modifications help applications to improve performance. Here an example on how a small modification helped a critical application to improve its performance without big refactorings.
I am very proud to be a Jazooner this year, my session "Tools and Tips to Diagnose Performance Issues" is scheduled to June, 24. I want to share with the audience my experience on diagnosing performance problems related to Java technology at server side applications.
If a machine does a simple test faster than machine B, is machine A the faster machine for your needs?
Premature optimization is the root of all evil. Writing badly-performing code is even worse.
It's impossible to tell performance without measuring
jmeter leads us down a blind alley -- should we have known better?
One connection good.
Then two connections better.
Or maybe not so.
Everything (almost) you wanted to know about tuning glassfish without reading the manual.
Sun has submitted a SPECjAppServer 2004 submission that scales across a lot of hardware. Is it just a question of throwing hardware at the problem?
Interested to see what awaits the client-side Java development in the near future?
You can inspect all objects stored in your browser cache, both memory and disk cache. Check that and other tricks about view layer optimizations in web applications.
Trying to reduce the number of Http connections required to load your web page? Check that.
Glassfish V1 was a price performance leader with good enough performance. Good enough is no longer enough.
Java has two switch statements -- should you actually care?
Thread pools can typically be dynamically resized, but is that a feature you should take advantage of? In a word -- no.