Java Application Profiling with the SAP JVM ProfilerThis site describes, why resource consumption and profiling is still an issue in Java. For the impatient: If you are already familiar with the related difficulties or Java profilers, you may test the SAP JVM Profiler as described below. Why profiling?At first glance Java is a comfortable programming language with regards to resource consumption: There is automatic memory management in place and the VM's just-in-time compiler takes care of generating machine code for fast application execution. Unfortunately this is only half the story. It is still easy to accidentally utilize large amounts of memory and CPU resources in Java. It is up to you as a developer to use inexpensive API calls and use appropriate algorithms and initialization strategies. Only if you have an impression of your application's resource consumption you can assess the scalability of your application in an application server environment. What's the SAP JVM Profiler good for?It will help you identify runtime bottlenecks, analyze the memory footprint of your application and find the code causing the problem. Even if you think your application behaves well, it's often valuable to see what happens "under the hood".
Want to know more before starting? Check the Features and Benefits page. What do you need to start?You need the SAP JVM Profiler backend, frontend and if you like some information:
|
Links Download the Eclipse archive version of the SAP JVM Profiler 1.6 Detailed download instructions for SAP JVM Profiler 1.6 Download the SAP NetWeaver Composition Environment Quickstart: Profile an application on the SAP NetWeaver Composition Environment View the SAP JVM Profiler documentation (PDF, 6 MB) |