lect5.ppt - 10/13/04 cis 4100 systems performance and evaluation lecture 7 by zornitza genova...

Lect5.ppt - 10/13/04

CIS 4100 Systems Performance and Evaluation

Lecture 7

byZornitza Genova Prodanoff

ZGP002

Lecture Outline

Chapter 5 – Planning the Capacity of Web Services

Adequate Capacity

Capacity Planning Methodology

Understanding the Environment

Workload Characterization

Workload Forecasting Performance Modeling and Prediction

ZGP003

Adequate Capacity

ZGP004

Capacity Planning Methodology

The methodology relies on:

• Workload Model

• Performance Model

• Cost Model

ZGP005

ZGP006

Capacity Planning Methodology

Phases of the methodology:

• Phase 1: Understanding the environment - learning what hardware, software, network protocols are present

ZGP007

ZGP008

ZGP009

ZGP0010

Capacity Planning Methodology

Phases of the methodology:

• Phase 2: Workload characterization – breaking the global workload into basic components is important, because basic components can be described with quantifiable parameters.

e.g. transaction arrival rates, service demand, etc.

ZGP0011

ZGP0012

Capacity Planning Methodology

Phases of the methodology:

• Phase 2: Workload characterization – many parameters are not measured directly, but are obtained by deriving their values from other (measurable) parameters.

ZGP0013

ZGP0014

ZGP0015

Capacity Planning Methodology

Phases of the methodology:

• Phase 2: Workload characterization – data collection issues: benchmarks or ROT maybe needed instead of raw measurements.

ZGP0016

ZGP0017

Capacity Planning Methodology

Phases of the methodology: • Phase 2: Workload characterization

Example 5.1 / Page 189

ZGP0018

Capacity Planning Methodology

Phases of the methodology:

• Phase 3: Workload validation – running synthetic workload and comparing results against the raw data results. If margin of error is within 10-30%, model is valid.

ZGP0019

Capacity Planning Methodology

Phases of the methodology:

• Phase 4: Workload forecasting – predicating how the system workload will change/vary in the future.

Example 5.2 / Page 191Example 5.3 / Page 194

Example 5.4 / Page 199 Solve the problem when throughput is only 600,324

1020 6