Escolar Documentos
Profissional Documentos
Cultura Documentos
TEEAM Region
Webex Series
Storage Sizing
for SAP
Cenk Ersoy
Advisory SE
cenk.ersoy@emc.com
WHAT IS SIZING
Sizing is the process of translating business needs into hardware
requirements
SAP sizing determines max hardware requirements based on sizing
KPIs such as CPU time, disk size/performance, memory size,
network bandwidth
Sizing is an iterative process
Sizing method is usually based on several assumptions (number of
users, documents processed per hour etc) make sure you
document/test your assumptions
Every vendor (or even every specialist at a vendor) may have its
own method of sizing
Copyright 2014 EMC Corporation. All rights reserved.
SIZING TYPES
Greenfield
Customer is implementing SAP for the first time
Estimate sizing using SAP QuickSizer and SAP Sizing Guidelines
(e.g. http://service.sap.com/quicksizing and
http://www.sap.com/bisizing )
Brownfield or post-go-live
Customer currently running SAP but looking to expand their
hardware capacity , add more users or re-platform
Extrapolate sizing from existing hardware and measured
utilization
Hybrid
Brownfield customer but looking to implement new SAP
components or newer release which will be Greenfield
Mix of approaches to sizing
Copyright 2014 EMC Corporation. All rights reserved.
Recommendation
Initial (Greenfield)
CAUTION
Do not rely simply on the output of the sizing tool. Factors such as
code customizing, parameter settings, usage behaviour, data
growth rate, data lifecycle policies and in-place datacenter
processes may affect the actual required sizing.
Get the input of business users as well (not just infrastructure
team).
For customer with very extensive code modifications, expert level
SAP sizing may be needed.
Sometime custom questionnaires may be used.
What is SAPS
SAP Application Benchmark Performance Standard
It is a hardware-independent unit that describes the performance of a system
configuration in the SAP environment.
SAPs are the number of SD dialog steps using transactions
VA01->VL01N->VA03->VL02N->VA05->VF01
that can be completed in one minute.
Since the benchmark has a built-in think time of 10 seconds between dialog steps,
each user can complete 60/(10+ RT) dialog steps per minute.
What is SAPS
SAPS
value is
closely
related to
CPU
power
Source: SAP AG
10
SAP Benchmarks
SAP works closely with hardware vendors and performs
benchmarks on different hardware configurations.
11
Source: SAP AG
Copyright 2014 EMC Corporation. All rights reserved.
12
13
CPU
Processing time
Cost factor number of servers and/or CPUs
Expressed in SAPS (www.sap.com/benchmark)
Rule of Thumb: 1:1 vCPU:pCore
Memory
Cost factor physical memory slots in server, DIMM size
Expressed in MB/GB
Rule of Thumb: No memory over-commitment. Dont forget
to consider consider OS, DB memory requirements
Disk
Needed to store data (SAP repositories - ABAP Code)
Cost factor amount of data, retention period, disk I/O, backup
Copyright 2014 EMC Corporation. All rights reserved.
14
Source: SAP AG
15
16
17
SAP QuickSizer
The customer works with a SAP consultant to define their initial
environment within QuickSizer.
QuickSizer has two independent models for sizing: User based and
throughput based
QuickSizer estimates CPU, memory and disk requirements.
Throughput based sizing is better for larger projects but usually
the customer lacks the input data (number of processed orders,
document sizes, online usage behaviour, background jobs etc)
It is better to use DB SAPS values from QuickSizer for storage
sizing
18
SAP QuickSizer
The CPU sizing result assumes 65% utilization. It is OS and
hardware independent
Disk size recommendation is based on the sizes of the DB tables in
the DB Data Dictionary in SAP. It is platform independent. Storage
sizing for binaries, images, temp areas and SAPMNT are not
considered in the disk space calculations.
Memory sizing is also hadware independent. Unicode is assumed.
19
Source: SAP AG
Copyright 2014 EMC Corporation. All rights reserved.
20
21
22
23
24
25
26
27
SAPS
3,00
5,000
4,000
SERVER
ERP - ECC
CRM
BW
SAPS
3,000
5,000
4,000
DB
SAPS
900
1,500
1,200
28
SERVER
ERP - ECC
CRM
BW
SAPS
3,000
5,000
4,000
DB
SAPS
900
1,500
1,200
APP
TYPE
OLTP
OLTP
OLAP
Front End
IO
540
900
1,080
29
SERVER
ERP - ECC
CRM
BW
SAPS
3,000
5,000
4,000
APP
DB SAPS
TYPE
900
OLTP
1,500
OLTP
1,200
OLAP
Front End
IO
540
900
1,080
F/E
F/E Read
Write
432
108
720
180
540
540
30
SAPS
3,000
5,000
4,000
APP
DB SAPS
TYPE
900
OLTP
1,500
OLTP
1,200
OLAP
Front End
IO
540
900
1,080
F/E Read
432
720
540
F/E
Write
108
180
540
For OLTP workload, we have 1152 host reads / 288 host writes (small random IO)
For OLAP worload, we have 540 host reads / 540 host writes (large block
sequential IO)
31
Assume a storage array read cache hit rate of 20% - 40% (assume the
larger value is you are proposing FASTCache.
32
If you do not have the storage array sizing tools (Poor Mans Approach J )
Convert OLAP large block IO (128KB) to OLTP small block IO (8KB);
take the front-end IOs write IO and multiply by RAID penalty factor for writes (4
for RAID5 and 2 for RAID1)
add the front end read IOs
the result will give you the backend IO value
finally define a tiered backend architecture with the following IOPS per drive
type:
3000 IO per SSD
180 IO per SAS/FC 15K
140 IO per SAS/FC 10K
60 IO per NLSAS/SATA (I personally do not recommend this tier)
Make sure that the capacity requirements are also met.
Copyright 2014 EMC Corporation. All rights reserved.
33
Sizing HANA
HANA is server based in-memory with storage used
as persistence level
Sizing is determined by SAP and the server vendor
CISCO
VCE
34
LANDSCAPE DESIGN
35
THANK YOU
36