• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Performance Bottleneck Identification
 

Performance Bottleneck Identification

on

  • 6,293 views

Presentation to illustrate process to identify performance bottlenecks in a J2EE application

Presentation to illustrate process to identify performance bottlenecks in a J2EE application

Statistics

Views

Total Views
6,293
Views on SlideShare
6,268
Embed Views
25

Actions

Likes
2
Downloads
0
Comments
0

5 Embeds 25

http://www.slideshare.net 9
http://guiaderutacamaracomercio2011.pbworks.com 7
http://www.linkedin.com 5
http://www.lmodules.com 3
http://www.docshut.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Performance Bottleneck Identification Performance Bottleneck Identification Presentation Transcript

    • Identifying Performance Bottlenecks
      Mustufa Batterywala
      Lead Performance Engineer
      http://batterywalam.wordpress.com/
    • 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?
    • 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
    • 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
    • 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
    • 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
    • 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
    • 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
    • Thanks!!!
      For any queries write to:
      mustufa2k2000@yahoo.com