Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Proactive performance management_what_is_all_about_v0.3


Published on

This presentation focuses on the importance of Proactive Performance Management and how one could implement Proactive Performance Management approaches on their programs.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Proactive performance management_what_is_all_about_v0.3

  2. 2. –Things to note –What Is Systems Performance Engineering –What are the activities involved in Systems Performance Engineering –What is Reactive Performance Management –What is Proactive Performance Management –What are the Benefits of Proactive Performance Management –The Proactive Performance Management Process –Where does Performance Testing fit in all of this –Q&A –Thanks for attending the session AGENDA
  3. 3. –Practical Performance Analyst is completely a volunteer driven effort. We welcome your contributions and donations which will help us support the on-going initiatives at Practical Performance Analyst. –We welcome opposing points of view. We request that you treat everyone on the call with respect and respect their points of view. Please take any personal discussions offline. –Please let us know if you are interested in helping out at Practical Performance Analyst. We’ve got a few open positions and can always do with some help. –Please put yourself on mute through the session. Please feel free to ask relevant questions. If the presenter is busy answering a question please write a short note and give the presenter an opportunity to respond. THINGS TO NOTE
  4. 4. Definition of Software Performance Engineering –Performance Engineering (SPE) is a systematic and quantitative approach for the cost-effective development of software systems to meet stringent Non Functional Requirements (Performance – Capacity –Scalability –Availability –Reliability –etc). –Dr.Connie Smith in her book onSoftware Performance Engineeringadvocates that, Performance Engineering is a software-oriented approach, focused on optimal selection of application architecture, design, and implementation choices with the objective of meeting Non Functional Requirements. –Software Performance Engineering can also be defined functionally as the set of tasks or activities that need to be performed across the Software Development Life Cycle (SDLC) to meet the documented Non Functional Requirements. Software Performance Engineering is often viewed as the art of building systems that meeting Non Functional requirements within the allocated time frame and budget constraints. WHAT IS SYSTEMS PERFORMANCE ENGINEERING
  5. 5. WHAT ARE THE ACTIVITIES INVOLVED IN SYSTEMS PERFORMANCE ENGG –At Requirements Gathering: Non Functional Requirements Gathering –At Design: Design for Performance & Performance Modelling –At Design: Capacity Planning –During Build: Unit Performance Testing & Code Optimization –During Build & Test: On-going Performance Testing –Nearing Go Live: Systems Performance Monitoring –Post Go Live: Performance Modelling & Capacity Management
  6. 6. –Performance Testing at Go Live –Determining Infrastructure Capacity Requirements at the end of Performance Test –Identifying major architectural concerns during performance test –Identifying major gaps in understanding of system workload at go live –Fixing System Performance issues in production –Addressing Compute, Storage & Network Capacity issues in production WHAT IS REACTIVE PERFORMANCE MANAGEMENT
  7. 7. WHAT IS PROACTIVE PERFORMANCE MANAGEMENT –At Requirements Gathering: •Document your workload models •Document your overall Non Functional Requirements •Document your Performance Engineering approach –At Design: •Review Design for Performance •Performance Modelling using Analytical Modelling techniques •Capacity Planning using Analytical Models & Existing Vendor Benchmarks –During Build: •Unit Performance Testing •Application Diagnostics & Code Optimization •Continuous On-going Tier Performance Test –Nearing Go Live: •End to End Systems Performance Testing •Application, Systems & Network Performance Monitoring
  8. 8. WHAT IS PROACTIVE PERFORMANCE MANAGEMENT …..CONTD –Post Go Live: •Ongoing Performance Modelling •Ongoing Capacity Management
  9. 9. –Good understanding of the overall approach to Performance Engineering across the program –Good understanding of the Compute, Storage & Network capacity required –Early identification of Architectural issues –Early visibility about challenges around procurement of tools, licensing, resources and timelines –Early visibility of overall system capacity requirements –Ability to identify code bottlenecks early on in the development life cycle –Ability to identify configuration and design related issues early on in the development life cycle –Ability to forecast application performance for increase in business workload –Ability to forecast system capacity requirements for increase in business workload –Ability to identify potential performance issues before they turn into show stoppers WHAT ARE THE BENEFITS OF PROACTIVE PERFORMANCE MANAGEMENT
  10. 10. –Performance Engineering Approach –Activities, Tooling, Environments, Resources –Workload Modelling –Non Functional Requirements –Capacity Plans for Compute, Storage & Network –Document, Review, Approve •Performance Testing Strategy •Capacity Management Strategy •Application Performance Management Strategy –On-going Unit Performance Testing, Application Diagnostics & Optimization –Performance Testing, Tuning & Optimization –Automate Systems Performance Monitoring & Application Performance Monitoring –Automate Performance Modelling & Capacity Management THE PROACTIVE PERFORMANCE MANAGEMENT PROCESS
  11. 11. –Performance Testing in the traditional sense: •Is a reactive approach to Performance Management •Is conducted post completion of SIT and before go live •Is conducted with minimal understanding of workload models •Is conducted with lack of understanding and agreement on Non Functional Requirements •Is conducted with inappropriate tools due to lack of funding •Is conducted with inadequate set of resources due to lack of funding •Is conducted in scaled down environments due to lack of funding –Performance Testing should ideally be conducted: •As early as possible during build •Should include Unit Performance Testing •Should include Tier Performance Testing •Should include proactive Application Diagnostics, Tuning & Optimization WHERE DOES PERFORMANCE TESTING FIT IN WITH ALL OF THIS
  12. 12. –We at Practical Performance Analyst would like to thank you for attending todays webcast –We value your input. Please take a minute and send us an email with your thoughts, input and feedback at –Please send us a list of topics that you would like us to include as part of our future webcasts –Practical Performance Analyst is completely a volunteer driven effort. We welcome your contributions and donations. –Please let us know if you are interested in helping out at Practical Performance Analyst. We’ve got a few open positions and can always do with some help. –Come work with us and help build a stronger global community of networked Performance Engineers THANKS FOR ATTENDING THE SESSION