You are on page 1of 26

Introduction to Sizing

Performance, Data Management & Scalability


SAP AG
Agenda

Scalability as the Basis for Sizing

Performance Indicators

Proving the Scalability

Sizing mySAP Business Solutions

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 2


Goal of Client Server Programming: Scalability

Thousands of users

Terabytes of data
High throughput
Large objects
scalability
Scalability 7*24h operation
High concurrency
Small system
Connected users
one user
one server worldwide
Many servers

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 3


Multi-Tier Architecture Optimization Potential
Optimization Potential
Load Layer What? Where?

Memory & Controls


10-20% CPU Consumption
Presentation
Network
Communication

Memory & Compression


5-10% CPU Consumption Templates
Internet
Network
Communication
Memory & Process Design
60-70% CPU Consumption Applications, Customizing
Application
Network Techn. Infrastructure
Communication DB
Memory &
10-20% CPU Consumption OS
Database Physical I/O

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 4


The Architecture of mySAP Solutions
Browser Browser

Web
Server
SAP SAP
GUI GUI
Approx.
10ms
2.6KB
ITS ICMAN

Dispatcher Gateway Dispatcher


10MB RFC
0.1ms Enqueue Trace
Trace
Shared
Memory WP
100 MB and
Buffer 0.01ms ENQ Enqueue WP
Trace SE30 WP Table
Buffers

SQL
20KB Trace 1ms
10 GB
DBWP DBMS

10ms
10GB 2 TB Database

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 5


Key Performance Indicators of Scalability & Sizing

With respect to Initial Cost of Ownership (ICO) and Total Cost of


Ownership (TCO)
Disk
When data can't be avoided
Backup/recovery depends on size of database
CPU
Processing time
Number of application servers/CPUs
Memory
User contexts
Buffers
Network runtime
Transferred amount of data
Costs for leasing bandwidth

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 6


Vertical Scalability

Multi-tier Internet architecture


One-tier: Laptop Demo System

Two-tier: Central Installation (database and application part on one


physical server), multiple presentation servers

Three-tier: One database server, multiple application servers and


multiple presentation servers

Multi-tier: One database server, multiple application servers multiple


presentation servers, mutiple Internet Transaction Servers
and multiple Web servers

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 7


Horizontal Scalability

Presentation Layer
More than 47,000 very active users connected to one database have
been tested

Internet Transaction Server and Web Server


More than 100 hits /sec

Application Layer
Up to 161 application servers have been tested successfully
The highest number of physical application servers at customer
installations is less than 30

Database Layer
Scalability through SMP architecture of the database server
More than 120 CPUs and more than 10 TB Database size
Scalability through parallel databases
Scalability through Components

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 8


How to Measure and Prove the Scalability

SAP Standard Application Benchmarks

Basic guidelines used for designing benchmarks


Generate reproducible and representative load
Generate scalable and configurable load
Available for all platforms but platform independent
Defined and controlled by SAP on behalf of the SAP Benchmark
Council
Represent typical processes in a customer environment
Measure throughput (in SAPS) and dialog response times
Analyze system configurations and parameter settings
Cannot reflect all customer environments

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 9


SAP Standard Application Benchmarks

mySAP Supply Chain Management mySAP Human Resources

Materials Management- MM Cross Application Time Sheets- CATS


Sales & Distribution- SD Payroll
Production Planning- PP
Warehouse Management - WM mySAP Financials
Assemble-To-Order - ATO Financial Accounting - FI
Advanced Planning and Optimizing - APO
Industry Solutions
mySAP Product Lifecycle Management
Retail
Project System - PS Banking - Bank Customer Accounts- BCA
Utilities - Customer Care and Service - CCS
mySAP Business Intelligence

Business Information Warehouse- BW mySAP Customer Relationship Mgmt


E-Selling
E-commerce Interaction Center
Online Store

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 10


Published Results for SD Benchmarks
(Highest Number of Users)

1993 1994 1995 1996 1997 1998 1999 2000 2001


25560 2002
50000
47528
45000 47008
Number of SD
40000
Benchmark users
35000

30000
26000
25560
25000 23000
24000
20000 19360
16440
15000
14400
10000
5320
5000 3700
1700 2000
120 300 710 1400
0

Three-tier Internet Architecture

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 11


Key Figures for the 47,528 SD User Benchmark

3,660 DB transactions per second (commits)


8,300 MB average disk write per second
75 MB average disk read per second
256 GB data blocks written in one hour
54 GB data blocks read in one hour
314,223 network packets per second with an average packet size of 859 bytes
151,250 statements and 51,620 rows inserted per second!
6,228 GB disk space
1,600 SAP transactions / second
3,999 Screen changes / second
Database used a 32-processors SMP server
R/3 was running on 424 processors
4,799,330 fully business processed order line items per hour ( 1,333 per second )

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 12


Definition: SAPS

S AP
A pplication Benchmark
P erformance
S tandard

2,000 fully processed 100 SAPS


order line items / hour*

SD Benchmark

* =^ 6,000 dialog steps and 2,000 postings or 2,400 SAP transactions

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 13


Agenda

Scalability as the Basis for Sizing

Performance Indicators

Proving the Scalability

Sizing mySAP Business Solutions

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 14


Factors that Influence Sizing

SAP and Partner Customer

Software Number
Version Performance / of users

Sizing Amount of Reporting


DB Version Reporting / Dialog /
Batch Batch

OS Version Load profile

Throughput Response
Hardware Times Customizing

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 15


Sizing vs. System Landscaping
Phase 1 Phase 2 Phase 3
Mapping business Translating business Implementing actual
requirements to requirements into high-level servers and
SAP solutions technical requirements infrastructure

Business background

Sizing Tool &


Algorithms

Key Processes and objects

Customers, partners, SAP Hardware vendors


in personal consulting Hardware independent server size
SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 16
Focus on Phase 2

Input
Translating business requirements into high-level technical
requirements
On the basis of tools and methods
Quick Sizer tool
T-Shirt sizing
Rule of thumb
Expert sizing, upgrade sizing, delta sizing

Output
Net hardware-independent requirements
Disk in GB
CPU in SAPS
Memory in MB (user-based only)
(Frontend Network load in kB per user interaction step)

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 17


Roles of Different Organizations

Customer Hardware Partner

Configuration proposal
Requirements

Experience
Productive
Customer
SAP
GoingLive

Tests
Check

Customer SAP Standard


Customer Load Profile Application Benchmarks
Configuration

Hardware
Sizing

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 18


The Sizing Process

Sizing is an
iterative process

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 19


Joint Sizing Project Since January 1997

Hardware partners are responsible for hardware configuration and


sizing

Quick Sizer (user-based) - live since August 1997

Quick Sizer (user/quantity structure-based) -


live since December 1997

Start of the User-based User/quantity Nearly 100,000


Sizing Project Quick Sizer structure-based Quick Sizing
LIVE Quick Sizer projects
LIVE

January 1997 August 1997 December 1997 November 2003

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 20


HW Sizing : Task of the Competence Center

Expectations Configuration
Variants
E
Response Times
D
Throughput C

SAPS
Load Profile
Load equivalent to
I
n FI n FF
I
MM
m SD m M
W
p D
S
m S FI
o MM n
p WM equivalent to xxxx SAPS
p WM Hardware
n FI
a P Configuration
a PP P
m SD for the customer

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 21


A Customer Can Perform More Than One Sizing

SAP Solution Manager in Implementation


Project Business Final Go Live &
Realization
Preparation Blueprint Preparation Support
Project Activities

Customizing
Define Business Synchronization End User
Project

ng
ng
Training and
ng
Definition Blueprint
Configuration Documentation

zi
zi
zi

Define Set-up Developments


Data

Si
Si
System
Si

of DEV
Transfer
Landscape Landscape Authorization

Testing

Sizing
Initial Expert
Plausibility
Sizing Sizing
Check,
Resizing
Tool support available No explicit tool support available
SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 22
Participating Technology Partners

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 23


Summary

Proven Scalability - with enough potential for future


growth

mySAP Business Solutions exploit the latest available


components

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 24


Questions?

Q&A

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 25


Copyright 2003 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of
Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli,
Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
ORACLE is a registered trademark of ORACLE Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and
other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.
JAVA is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.
MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names mentioned are trademarks of their respective
companies.

SAP AG 2003, Internal sizing info session, PDMS, SAP AG / 26