Quick SizerUser Throughput

5/28/2018 Quick SizerUser Throughput

1/19

Sizing by Users and by Throughput

SAP AG / Performance & Scalability

2012


2/19

2012 SAP AG. All rights reserved. 2

Learning Objectives

After this session you should be able to:

Tell the different scopes of user and throughput sizing

Know when to use which approach Understand the basic sizing algorithms for both sizing approaches


3/19


Agenda

Sizing Key Performance Indicators

User-based Sizing

Throughput-based Sizing


4/19


Sizing-Relevant KPIs (Key Performance Indicators)

CPU

Disk Size

Disk I/O

Memory

Network

Load

Processing times of business transactions or tasks

Cost factor: Number and processing power of servers

Data that resides on the database

File read and write activity to storage

Cost factors: Backup/recovery depends on size of database

Allocated to a user or background process

Garbage collection, acceleration, planning capabilities, buffers, caches

Cost factor: Physical memory slots

Transferred amount of data

Network time and roundtrips

Cost factor: Leasing bandwidth


5/19


Goal of Sizing: Find the Peak Load Requirements in Terms

of Sizing KPIs

How to achieve this goal?

Find out the point in time when the maximum available

resources of the configuration are needed

May be different times for CPU, memory, disk I/O

May be different for DB and application layer

Find out usage patterns

Of users

Of processes, maybe background


6/19


Different End User Access Different Usages

Example from SAP CRM

Backend Systems

ERP

SCM

BW

Legacy

Possible user accesses

CRM Server

CRM Enterprise

Middleware

Adapter

Interaction Center Telephony / E-mail

Internet Shop

Web server

Service engineers Mobile handhelds

Mobile Sales Mobile clients

Intranet

Different UIs


7/19


Text

Two Different/Separate Sizing Strategies with Different

Goals

Advantages Users are relatively easy to

determine

Memory is driven by user

contexts

Challenges

Define user

Determine user load patterns

Sizing DB growth by users

Sizing by Users Sizing by Throughput

Advantages Scenario, transaction

Based on actual business

objects and scenarios

Peak/Average sizing

Challenges Obtaining the right figures


8/19


Design Guidelines: Two Parallel Approaches of Quick Sizer

Users

Low, medium, high activity

Application components Assumptions for load on CPU and disk

Result

Average CPU

Disk size

Disk I/O Memory

Quick Sizer

Business throughput

Considers t ime periods

Residence time

Average working day

Peak load time frame

Result

Average and peak CPU

Disk size and growth

Disk I/O

Memory

Sizing based on users Sizing based on throughput


9/19


Agenda

Sizing Key Performance Indicators

User-based Sizing

Throughput-based Sizing


10/19


Goal Number 1: Define a User

Possible definitions

System access mode (handheld, online, )

Different roles

Distinguish different applications

One person may have numerous modes open

Logged-on users

Internet Shop users browse

through the catalog

00-24

17-19

06-09

15-18

09-18

CRM Server

CRM Enterprise

Middleware

Adapter

Interaction Center Telephony / E-mail

Internet Shop Web server

Service engineers Mobile handhelds

Mobile Sales Mobile clients

Intranet Different UIs

09-22


11/19


Goal Number 2: Find Out the Usage Patterns That Most

Affect Sizing

User sizing volume drivers are a combination of

User activity in terms of think time

Application type including complexity of business

process design

Access type to application


12/19


Examples of User Sizing in the Quick Sizer

Standard user sizing

For each application component the number of

Low activity users process 12 interaction steps per hour

Medium activity users

process 120 interaction steps per hour

High activity users

process 360 interaction steps per hour

Avg. TT= 300 s

Avg. TT= 30 s

Avg. TT= 10 s

SAP offers some standard assumptions users with low, medium, and high

levels of activity.


13/19


Examples of Other User Sizing in the Quick Sizer

SAP CRM Mobile Sales users

Max. Number of logons per hour

Each user gets a CPU weight and memory

Enterprise Portal users Initially weighted applications, can be modified

Think time can be freely assigned (custom-specific)


14/19


How to Obtain the Number of Users

Often, customers suppose a higher activitythen there really is Coffee breaks are not included

Think time refers to interaction steps with theapplication server, not necessarily the screen changes

Users may not only use SAP systems

User sizing tips Take concurrently active users per application

If you do not know how active they will be, take mediumactivity

To be on the safe side, take the maximum number of

users at any one time (snap shot) There is no ratio between named and concurrent users


15/19


Number of Named Users and Concurrent Users

Company Named Users Concurrent Users

Owens Corning 7000 1200

Ruhrkohle 6471 1750Georgia Pacific 6240

BFI 5000

Eli Lilly 5000 2500

Swisscom AG 4274

Dow Corning 4000

Wacker Chemie 4000 2500VEW AG 2633

Intel Corp. 2506

BostonSci 2500 1900

DeTe Mobil 2500 1500

International Paper Company 2201

GTE 2000 150Schering AG 1970

Degussa AG 1895

Olin Corporation 1857

Electrabel SA 1699

Veag 700 500

Colgate 3000

2000

Grainger 9000 5500

There is no fixed

ratio between

named and

concurrent users


16/19


Dialog

Business Scenario*

Rel.CPU-Usage/Dialog

Step

DatabaseUpdate

0.00

1.00

2.00

3.00

4.00

5.00

6.00

FI SD PP MMN ATO

84%

81%

79%

82%

68%

8%9%

7% 7%

10%

8%

9%14% 11%

22%

Platform & Release Dependent

*SAP Standard Application Benchmarks based on R/3 Enterprise 4.70

Load Comparison of Business Scenarios


17/19


Understand the Result of User-Based Sizing

User sizing in the Quick Sizer renders

CPU sizing (SAPS)

Reflects usage pattern, attributes specific load per application

Formula: User * SAPS_factor_application

Memory sizing in MB

Formula: User * x_MB

Disk sizing in MB

Assumes several MB per user per workday

Formula: Users * disk_MB * workdays

Disk I/0

Formula: System SAPS * weighting factor


18/19


Additional Information

http://service.sap.com/sizing Sizing methodology

Sizing guidelines

Sizing decision tree

http://service.sap.com/quicksizing

Free online tool to use

Basis for hardware vendors sizings

http://www.sap.com/sizing


19/19

Documents

Quick SizerUser Throughput