Bottlenecks limit application performance and can be caused by hardware, software, or network resources. Identifying bottlenecks in complex J2EE applications requires various tools. The process involves running load tests using diagnostic tools to identify bottleneck layers and components, then using profilers to debug problematic code. Monitoring application server heap usage and server resource consumption also helps identify bottlenecks.

1. Identifying Performance Bottlenecks Mustufa Batterywala Lead Performance Engineer http://batterywalam.wordpress.com/

2. A bottleneck is any resource hardware, software or network that limits the performance of an application These are found at each and every tier/component of an application Resolving the bottlenecks requires special tools and skills What is a bottleneck?

3. Response times get slower In efficient resource utilization Application is not scalable Supports less number of concurrent users Loss in business revenue due to less customer satisfaction System crash Impact of Performance bottlenecks

4. J2EE applications are very complex Presence of multiple components and layers Complex code written by multiple teams Large spectrum of technologies Challenges in Identifying Bottlenecks in J2EE

5. Load Testing tools HP Load Runner, Jmeter, SandStorm Profilers Yourkit, Jprobe, JProfiler Diagnostic tools HP Deep diagnostics, Dynatrace, InfraRed GC Analyzers jConsole, HP jtune, Resource monitoring tools Windows perfmon, vmstat, JMX, SNMP monitors Tools for Identifying Bottlenecks in J2EE

6. Run the load tests to measure the current performance of an application Use a diagnostic tool during the load test to identify bottleneck layers/components Use the profiler to further debug the problematic code and fix it Monitor and analyze the heap usage of the app server Monitor and analyze the resource consumption of the servers on which application being tested is deployed Process of Identifying Bottlenecks in J2EE

7. Can be used during load test Provides tier wise breakdown of transaction response times Helps in identifying the bottleneck component, tier Less overhead on the system under test Diagnostic tools

8. Provides information on method executions, call traces, memory utilization, thread execution details Helps in identifying the bottleneck in a particular section of code Has a huge overhead on the system under test Profilers

9. Thanks!!! For any queries write to: mustufa2k2000@yahoo.com