Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have developed a Java EE application and it will be in production soon.
Before that I’m trying to find bottlenecks inside this application.
I found this site:
http://www.slideshare.net/batterywalam/performance-bottleneck-identification
Please refer to the screen shot there.
Could anyone please tell me what Diagnostic tools are and what the difference is between a diagnostic tool and a profiler? Do we need to use both of them?
Usually a diagnostic tool is used to troubleshoot a specific problem once it has been identified, or to give you a wide range of stats about the overall performance of your code.
A profiler, on the other hand, is used to show what you’re looking for specifically (bottlenecks). It shows how long each call in your application is taking, so that you can easily identify areas that will be long running or should be re-examined for purposes of optimization.
Once you’ve determined where your trouble spots are using the profiler, you can use diagnostic tools to get more insight/ideas about why the code is slow and possibly to diagnose what the root cause of that problem is (long SQL calls, slow processing of large results sets, etc).