Ashraf Abu-Aisheh wrote:I am working on a big application "Banking System" and I am suffering from the performance, memory, heap ,... etc problems
Therefor, am searching for the best java Profiler to know where are the problems in my code.
The only thing I'd add to the good advice you've been given is that you shouldn't expect a profiler to solve your problems. If (as it sounds) you've got lots of such problems, then it may indicate more fundamental issues with the code than just what you see; and trying to solve them piecemeal (which is what a profiler will help you do) may not in fact solve anything at all.
A profiler is a diagnostic tool: it will help you find symptoms; it
won't help find the underlying cause (or causes).
Winston