Performance Engineering

From Guidance Share
Jump to navigationJump to search

- J.D. Meier

Performance Overlay

Performance Engineering includes specific performance related activities.

Key Activities in the Life Cycle

This Performance Engineering approach extends these proven core activities to create performance specific activities. These include: These include

  • Performance Objectives. Setting objectives helps you scope and prioritize your work by setting boundaries and constraints. Setting performance objectives helps you identify where to start, how to proceed, and when your application meets your performance goals.
  • Budgeting. Budget represents your constraints and enables you to specify how much you can spend (resource-wise) and how you plan to spend it.
  • Performance Modeling. Performance modeling is an engineering technique that provides a structured and repeatable approach to meeting your performance objectives.
  • Performance Design Guidelines. Applying design guidelines, patterns and principles which enable you to engineer for performance from an early stage.
  • Performance Design Inspections. Performance design inspections are an effective way to identify problems in your application design. By using pattern-based categories and a question-driven approach, you simplify evaluating your design against root cause performance issues.
  • Performance Code Inspections. Many performance defects are found during code reviews. Analyzing code for performance defects includes knowing what to look for and how to look for it. Performance code inspections to identify inefficient coding practices that could lead to performance bottlenecks.
  • Performance Testing. Load and stress testing is used to generate metrics and to verify application behavior and performance under normal and peak load conditions.
  • Performance Tuning. Performance tuning is an iterative process that you use to identify and eliminate bottlenecks until your application meets its performance objectives. You start by establishing a baseline. Then you collect data, analyze the results, and make configuration changes based on the analysis. After each set of changes, you retest and measure to verify that your application has moved closer to its performance objectives.
  • Performance Health Metrics. Identity the measures, measurements, and criteria for evaluating the health of your application from a performance perspective.
  • Performance Deployment Inspections. During the deployment phase, you validate your model by using production metrics. You can validate workload estimates, resource utilization levels, response time, and throughput.
  • Capacity Planning. You should continue to measure and monitor when your application is deployed in the production environment. Changes that may affect system performance include increased user loads, deployment of new applications on shared infrastructure, system software revisions, and updates to your application to provide enhanced or new functionality. Use your performance metrics to guide your capacity and scaling plans.


  • Performance Engineering Overview


Performance Modeling

Performance Design Guidelines

Performance Design Inspections

Performance Code Inspections


  • How To Instrument Your Application

Performance Testing

  • Performance Testing Guidelines
  • Performance Testing Overview
  • How To Load Test WebApplications
  • How To Model A Workload
  • How To Stress Test WebApplications

Performance Tuning

  • How To Identify WebApplication Bottlenecks
  • How To Tune ASPNET
  • How To Tune NET Framework
  • How To Tune SQL Server 2000
  • How To Tune Web Services
  • How To Tune Your Application
  • How To Tune Your Server

Building Codes


Recommendations address "what to do", "why", and "how." The recommendations are principle-based and they are organized using categories for easy consumption.


.NET Framework 2.0

.NET Framework 1.1


Checklist items present a verification to perform ("what to check for", "how to check" and "how to fix"). The checklist items are principle-based and they are organized using categories for easy consumption.


.NET Framework 2.0

.NET Framework 1.1

Related Items