Introduction to Experimental Design

Similar documents
Common Mistakes and How to Avoid Them

The Art of Workload Selection

Types of Workloads. Raj Jain. Washington University in St. Louis

Common Mistakes and How to Avoid Them

OPERATING SYSTEMS. Systems and Models. CS 3502 Spring Chapter 03

Common Mistakes in Performance Evaluation

A Systematic Approach to Performance Evaluation

Algunos de los comentarios de las páginas se han extraido de los textos:

Improving Throughput and Utilization in Parallel Machines Through Concurrent Gang

How Much Bigger, Better and Faster?

Bed Management Solution (BMS)

Introduction to Real-Time Systems. Note: Slides are adopted from Lui Sha and Marco Caccamo

System performance analysis Introduction and motivation

SE350: Operating Systems. Lecture 6: Scheduling

Oracle Financial Services Revenue Management and Billing V2.3 Performance Stress Test on Exalogic X3-2 & Exadata X3-2

Toward an Energy-Proportional Building Prospect

Announcements. Program #1. Reading. Is on the web Additional info on elf file format is on the web. Chapter 6. CMSC 412 S02 (lect 5)

Software Measurement

Towards Resource-Efficient Cloud Systems: Avoiding Over-Provisioning in Demand-Prediction Based Resource Provisioning

8l 10 g Productivity Engineering in the UNIXt Environment. An Empirical Investigation of Load Indices for Load Balancing Applications

Experimentation / Exercise / Use

Advanced Operating Systems (CS 202) Scheduling (2)

A FRAMEWORK FOR CAPACITY ANALYSIS D E B B I E S H E E T Z P R I N C I P A L C O N S U L T A N T M B I S O L U T I O N S

Reference model of real-time systems

comp 180 Lecture 04 Outline of Lecture 1. The Role of Computer Performance 2. Measuring Performance

A Profile Guided Approach to Scheduling in Cluster and Multi-cluster Systems

Skateboard Assembly Line Balancing High School Student Worksheet

Project Management: Project Justification and Planning

Clock-Driven Scheduling

Performance Analysis of Computer Systems

Test-king.P questions P IBM B2B Integration Technical Mastery Test v1

See Capacity and Performance across your IT enterprise

CS 111. Operating Systems Peter Reiher

On Cloud Computational Models and the Heterogeneity Challenge

FIFO SJF STCF RR. Operating Systems. Minati De. Department of Mathematics, Indian Institute of Technology Delhi, India. Lecture 6: Scheduling

Technology: Rack Mounted Servers

CS 147: Computer Systems Performance Analysis

Capacity Management from the ground up

Understanding the Behavior of In-Memory Computing Workloads. Rui Hou Institute of Computing Technology,CAS July 10, 2014

Chapter 1:Introduction to Design of Experiments

Chapter 6: CPU Scheduling. Basic Concepts. Histogram of CPU-burst Times. CPU Scheduler. Dispatcher. Alternating Sequence of CPU And I/O Bursts

CS 153 Design of Operating Systems Winter 2016

Click here to advance to the next slide.

An Automated Approach for Recommending When to Stop Performance Tests

File System Trace Replay Methods Through the Lens of Metrology

NaviCloud Sphere. NaviCloud Pricing and Billing: By Resource Utilization, at the 95th Percentile. A Time Warner Cable Company.

IBM. Processor Migration Capacity Analysis in a Production Environment. Kathy Walsh. White Paper January 19, Version 1.2

Modeling Trust in Critical Systems with Möbius KEN KEEFE SENIOR SOFTWARE ENGINEER LEAD MOBIUS DEVELOPER

Ricardo Rocha. Department of Computer Science Faculty of Sciences University of Porto

New IBM eserver p5 Systems - the Real POWER Changing the UNIX World

Cluster Workload Management

Oracle Communications Billing and Revenue Management Elastic Charging Engine Performance. Oracle VM Server for SPARC

A WORKLOAD GENERATOR FOR DATABASE SYSTEM BENCHMARKS. Hoe Jin Jeong and Sang Ho Lee

End-To-End Scaling: The Response Time Pipe

z/os Performance Case Studies on zhpf & Coupling Facility Paulus Usong, IntelliMagic Performance Consultant

CS5239 Computer System Performance Evaluation

cs465 principles of user interface design, implementation and evaluation

End-To-End Scaling: The Response Time Pipe

Software Measurement

Real-Time Systems. Modeling Real-Time Systems

Reading Reference: Textbook: Chapter 7. UNIX PROCESS SCHEDULING Tanzir Ahmed CSCE 313 Fall 2018

CPU SCHEDULING. Scheduling Objectives. Outline. Basic Concepts. Enforcement of fairness in allocating resources to processes

Sizing and Scoping your QRadar SIEM. Adam Frank Chief Client Success Architect. Robert McGinley SWAT Security Intelligence Architect

Cyberlab skills programme December 2011 Prepared by C Marais. Formative assessment. Summative assessment. Page in learner study guide

Analytical Development Using Quality by Design

IJCSC VOLUME 5 NUMBER 2 JULY-SEPT 2014 PP ISSN

LOAD SHARING IN HETEROGENEOUS DISTRIBUTED SYSTEMS

CPU Scheduling. Chapter 9

An operating system executes a variety of programs: Batch system - jobs Time-shared systems - user programs or tasks

Recovery Contract Negotiations. NEDRIX 2/24/04 Cliff Leavitt CBCP Sr Mgr BC / DR Staples

test workload real workload synthetic workload

Multi-Resource Packing for Cluster Schedulers. CS6453: Johan Björck

Addressing the I/O bottleneck of HPC workloads. Professor Mark Parsons NEXTGenIO Project Chairman Director, EPCC

Answers For Management Positions

Sizing SAP Hybris Billing, pricing simulation Consultant Information for Release 1.1 (et seq.) Document Version

A Paper on Modified Round Robin Algorithm

CPU Scheduling. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University

zenterprise Platform Performance Management: Overview

RealCareer Welding Solutions

E-BUSINESS SUITE APPLICATIONS R12 (12.1.3) EXTRA- LARGE PAYROLL (BATCH) BENCHMARK - USING ORACLE11g ON AN IBM Power System S824

Avoiding Specification Pitfalls!

Ability. Verify Ability Test Report. Name Ms Candidate. Date.

Lecture 11: CPU Scheduling

AWS vs. Google Cloud Pricing

Design of a Performance Measurement Framework for Cloud Computing

Information Systems 202. Regent Business School

Session-2: Deep Drive into Non Functional Requirements (NFRs)

E-tray: Administrators

BANK SECRECY ACT. Kevin T. Kane, President Financial Regulatory Consulting, Inc. April 19, frcconsult.com 1

Simulation Using. ProModel. Dr. Charles Harrell. Professor, Brigham Young University, Provo, Utah. Dr. Biman K. Ghosh, Project Leader

CPU Scheduling. Jinkyu Jeong Computer Systems Laboratory Sungkyunkwan University

Chapter 1: What is Economics? Section 1

Testing 2. Testing: Agenda. for Systems Validation. Testing for Systems Validation CONCEPT HEIDELBERG

GRID RESOURCE AVAILABILITY PREDICTION-BASED SCHEDULING AND TASK REPLICATION

Addressing UNIX and NT server performance

CPU Scheduling. Jinkyu Jeong Computer Systems Laboratory Sungkyunkwan University

Compensating Wage Differentials

Avoid Paying The Virtualization Tax: Deploying Virtualized BI 4.0 The Right Way

CPU Scheduling (Chapters 7-11)

The Evolution of Big Data

Transcription:

Introduction to Experimental Design Raj Jain Washington University in Saint Louis Saint Louis, MO 63130 Jain@cse.wustl.edu These slides are available on-line at: http://www.cse.wustl.edu/~jain/cse567-08/ 16-1

Overview! What is experimental design?! Terminology! Common mistakes! Sample designs 16-2

How to: Experimental Design and Analysis! Design a proper set of experiments for measurement or simulation.! Develop a model that best describes the data obtained.! Estimate the contribution of each alternative to the performance.! Isolate the measurement errors.! Estimate confidence intervals for model parameters.! Check if the alternatives are significantly different.! Check if the model is adequate. 16-3

Example Personal workstation design 1. Processor: 68000, Z80, or 8086. 2. Memory size: 512K, 2M, or 8M bytes 3. Number of Disks: One, two, three, or four 4. Workload: Secretarial, managerial, or scientific. 5. User education: High school, college, or postgraduate level. Five Factors at 3x3x4x3x3 levels 16-4

Cartoon 16-5

Terminology! Response Variable: Outcome. E.g., throughput, response time! Factors: Variables that affect the response variable. E.g., CPU type, memory size, number of disk drives, workload used, and user's educational level. Also called predictor variables or predictors.! Levels: The values that a factor can assume, E.g., the CPU type has three levels: 68000, 8080, or Z80. # of disk drives has four levels. Also called treatment.! Primary Factors: The factors whose effects need to be quantified. E.g., CPU type, memory size only, and number of disk drives. 16-6

Terminology (Cont)! Secondary Factors: Factors whose impact need not be quantified. E.g., the workloads.! Replication: Repetition of all or some experiments.! Design: The number of experiments, the factor level and number of replications for each experiment. E.g., Full Factorial Design with 5 replications: 3 3 4 3 3 or 324 experiments, each repeated five times.! Experimental Unit: Any entity that is used for experiments. E.g., users. Generally, no interest in comparing the units.! Goal - minimize the impact of variation among the units. 16-7

Terminology (Cont)! Interaction Effect of one factor depends upon the level of the other. 16-8

Common Mistakes in Experimentation! The variation due to experimental error is ignored.! Important parameters are not controlled.! Effects of different factors are not isolated! Simple one-factor-at-a-time designs are used! Interactions are ignored! Too many experiments are conducted. Better: two phases. 16-9

Types of Experimental Designs! Simple Designs: Vary one factor at a time " Not statistically efficient. " Wrong conclusions if the factors have interaction. " Not recommended.! Full Factorial Design: All combinations. " Can find the effect of all factors. " Too much time and money. " May try 2 k design first. 16-10

Types of Experimental Designs (Cont)! Fractional Factorial Designs: Less than Full Factorial " Save time and expense. " Less information. " May not get all interactions. " Not a problem if negligible interactions 16-11

A Sample Fractional Factorial Design! Workstation Design: (3 CPUs)(3 Memory levels)(3 workloads)(3 ed levels) = 81 experiments 16-12

Summary! Goal of proper experimental design is to get the maximum information with minimum number of experiments! Factors, levels, full-factorial designs 16-13

Exercise 16.1 The performance of a system being designed depends upon the following three factors: " CPU type: 68000, 8086, 80286 " Operating System type: CPM, MS-DOS, UNIX " Disk drive type: A, B, C a. There is significant interaction among factors. b. There is no interaction among factors. c. The interactions are small compared to main effects. 16-14