Performance Bottleneck Identification
12 likes8,471 views
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.
Performance Bottleneck Identification
- 1. Identifying Performance BottlenecksMustufa BatterywalaLead Performance Engineerhttp://batterywalam.wordpress.com/
- 2. A bottleneck is any resource hardware, software or network that limits the performance of an applicationThese are found at each and every tier/component of an applicationResolving the bottlenecks requires special tools and skillsWhat is a bottleneck?
- 3. Response times get slowerIn efficient resource utilizationApplication is not scalableSupports less number of concurrent usersLoss in business revenue due to less customer satisfactionSystem crashImpact of Performance bottlenecks
- 4. J2EE applications are very complexPresence of multiple components and layersComplex code written by multiple teamsLarge spectrum of technologiesChallenges in Identifying Bottlenecks in J2EE
- 5. Load Testing toolsHP Load Runner, Jmeter, SandStormProfilersYourkit, Jprobe, JProfilerDiagnostic toolsHP Deep diagnostics, Dynatrace, InfraRedGC AnalyzersjConsole, HP jtune, Resource monitoring toolsWindows perfmon, vmstat, JMX, SNMP monitorsTools for Identifying Bottlenecks in J2EE
- 6. Run the load tests to measure the current performance of an applicationUse a diagnostic tool during the load test to identify bottleneck layers/componentsUse the profiler to further debug the problematic code and fix itMonitor and analyze the heap usage of the app serverMonitor and analyze the resource consumption of the servers on which application being tested is deployedProcess of Identifying Bottlenecks in J2EE
- 7. Can be used during load testProvides tier wise breakdown of transaction response timesHelps in identifying the bottleneck component, tierLess overhead on the system under testDiagnostic tools
- 8. Provides information on method executions, call traces, memory utilization, thread execution detailsHelps in identifying the bottleneck in a particular section of codeHas a huge overhead on the system under testProfilers
- 9. Thanks!!!For any queries write to:mustufa2k2000@yahoo.com