011000358700000723482010 e

Sizing Methods and Tools –An IntroductionSebastian Schmitt SAP AG / Performance & Scalability2013

© 2013 SAP AG. All rights reserved. 2Customer

Agenda

Introduction to Sizing Methods

Sizing Tools

Factors that influence Sizing

Sizing on the Service Marketplace

Conclusion


Actual Customer Requests in the Area of Sizing

Definition Sizing

Translate business requirements into hardware requirements – in an iterative process

Typical sizing questions / statements

“Can SAP software payroll 3+ million employees and pensioners in less

than two hours?

Can SAP software payroll 3+ million employees and pensioners in less than two hours?“When I check your sizing Portal, there is no sizing guideline for

FIN-FSCM-TRN. How can I do a sizing?

“We are running on 4.6C and want to upgrade to ERP2005

We have 30,000 business partners and 60,000 sales orders with 50 line items per month. How much hardware does our SAP application require“


Sizing-Relevant KPIs (Key Performance Indicators)

CPU

Disk SizeDisk I/O

Memory

Network Load

Processing times of business transactions or tasksCost factor: Number and processing power of servers

Data that resides on the databaseFile read and write activity to storageCost factors: Backup/recovery depends on size of database

Allocated to a user or background processGarbage collection, acceleration, planning capabilities, buffers, cachesCost factor: Physical memory slots

Transferred amount of dataNetwork time and roundtripsCost factor: Leasing bandwidth


Different Times, Different Phases, Different Goals of Sizing

1. Very early to plan hardware expenditures2. A few months before live start to verify assumptions

Determine the overall performance requirements

3. During production stages to ensure operations and verify/adjust estimations made earlier. ”Trigger events” include:

Upgrade database, operating system, SAP applicationReconfigure system landscape Change business processRollouts: more users or other load

Project Preparation

Business Blueprint Realization Final

PreparationGoing Live &

Support

Upgrade Migration Business Units Functional Changes

GoLive

Sizing takes place in different phases of a project


Hardware Budget Sizing Advanced Sizing Expert SizingSmaller companies

Very simple algorithmsAssumptions, likelihoodsLevel setting of projectRisk identification

Medium to large companiesThroughput estimatesQuestionnaires, formulas Usage of standard toolsFocus on core business processes

Large or complex projectsCustom calculationsAnalysis of custom coding Custom sizing guidelines

Possible Definitions for Different Types of Sizing

All projectsSAP system monitors

Goal: Extend an existing system by load

e.g. by volume: 100 additional users who'll do the same as the current ones


Goal: Extend an existing system by functions

By different functions, e.g. you are live with CRM and want to add SCM


SAP NotesGoal: Upgrade SAP software

Re-Sizing Delta Sizing Upgrade Sizing

Production Sizings

GoLive

Initial Sizings


Agenda


Sizing Tools



Conclusion


Standard Sizing Methods and Tools

Initial Calculation MethodEducated guess

T-Shirt SizingSimple algorithms with many assumptions

FormulasSimple or more complex

Questionnaire without formulasFor structured questions

Quick SizerSupports user-based and throughput-based sizing


DisadvantagesMust include many assumptions”Educated” guess

Sizing Approach: Initial Calculation Method

1 Initial Calculation Method

AdvantagesQuick & easy Delivers ballpark estimate

Example

Need to process 5000 advertisements per weekMake assumptions

5 work days per week, 8 hour work day 5000/(5*8) = 125 ads per hour (250 ads during peak times)5 dialog steps to process 1 advertisementMax. server processing time per dialog step: 1 sec.Calculation: 250 ads * 5 DS * 1 sec processing time = 1250 sec. CPU capacity (1h): 3600 sec


DisadvantagesMust include many assumptionsUsually does not reflect customer reality

Sizing Approach: T-Shirt

2 T-Shirt

AdvantagesQuick & easy to understandFunctional & architectural information

Example (Excerpt from IPC Sizing Guide)


DisadvantagesSuggests an accuracy that sizing cannot deliverCan easily be misunderstood by inexperienced readers

Sizing Approach: Formula

3 Formula

AdvantagesIs closer to customer realityAllows for more variablesRelatively transparent approach

Example (Excerpt from Front-end Network Requirements)


DisadvantagesSAP must be contacted for a resultVersioning

Sizing Approach: Offline Questionnaire

4 Offline Questionnaire

AdvantagesDetailed customer information for a proper sizing Relatively transparent approachMore detailed level

Example (Excerpt from SEM Banking Questionnaire)


DisadvantagesOnly available online

Sizing Approach: Quick Sizer

5 Quick Sizer

AdvantagesSelf-service application on SMPAlways up-to-dateContains several different applications & componentsWidely recognizedAvailable 24/7, free usageLink to GoLive check

Example (Excerpt from Quick Sizer – SAP CRM)


Process for a Quick Sizing – Overview

Access Quick Sizer, create a sizing project and enter the data

Quick Sizer calculates the input and provides sizing result

Check for sample configurations at www.sap.com/benchmark

Provide hardware vendor with sizing project name. HW vendor proposes a configuration


Agenda


Sizing Tools



Conclusion


Some Factors That Influence Sizing

System Settings

ParameterizationInterfacesSecurity settingsUnicodeA2A, B2B scenario

Set up of business processesOrganizational structuresBusiness process design

CustomizingHW Platform

Processor technologyDisk technologyNetwork technologySystem infrastructure

User BehaviorConcurrencyLAN/WANInternet/intranetActivity, e.g.

*-SearchEfficient navigation

Avoiding dataArchiving strategiesInformation Lifecycle Management

Data VolumeTime for volume processingBackground processing, parallel jobsReporting

Disk Growth

SAP Software

ReleaseOLTP or OLAPIndustry solutions

Custom Coding, 3rd Party

Performance impactScalabilityBusiness process design

Technology Partner CustomerSAPResponsibility of

Customer profile

Customer profile


Three-Party Collaboration Model

ContributionsCertified benchmarks scalable hardwareDifferent configurations together with technology partnersPerformance studiesCustom load tests in collaboration with customersService level agreements

Expectations from benchmarking and sizing

Optimal performanceSuggestion for hardware configuration

Contributions Response time requirementsThroughput requirementsProvides business data input

ContributionsDevelopment and provision of benchmark toolkitsRegression testing for new releasesStandard sizing guidelines as part of quality assurance processSizing verification processes

Hardware Vendors Customer

SAP

Sizing RecommendationCPU (SAPS) Memory (GB)Database space (GB)Disk I/O operations per secFrontend bandwidth mbps

Three parties collaborate in the benchmarking and sizing process


Risks in a Sizing Project

The challenge in any sizing project is to obtain sufficient usage informationOften caused by communication issuesWhen there is not sufficient data available, assumptions must be made – and documented

INCOMPLETE INPUT DATA

While it is perfectly ok to work on assumptions you must ensure that a verification process is included in the project plan

ASSUMPTIONS ARE NOT VERIFIED

Are very hard to predict: Make sure there is a verification processMake sizing measurements, if required

CUSTOM CODING & SPECIAL DATA CONSTELLATIONS

Ris

ks in

a S

izin

g Pr

ojec

t


Agenda


Sizing Tools



Conclusion

Where to find information about Sizing?


SAP Service Marketplacehttp://service.sap.com/sizing

GuidelinesGeneral proceduresApplication-specific

ToolsQuick SizerSizing Decision treeOthers

Training opportunities

FAQs


Quick Sizer on SAP Service Marketplacehttp://service.sap.com/quicksizer


Sizing Guidelines on SAP Service Marketplace


Sizing Training & Events on SAP Service Marketplace


Sizing FAQs on SAP Service Marketplace


Agenda


Sizing Tools



Conclusion


Summary

Sizing means translating business requirements into hardware requirementsThe sizing process (and thus the sizing result) is closely tied to the lifecycle of the softwareAnd therefore an iterative exerciseThe success of the sizing exercise almost entirely depends on the quality of the data– "Garbage-in, garbage out"

Sizing involves very different people and teams within an organizationExpert sizing is recommended for custom development


Additional Information

http://service.sap.com/sizingSizing methodologySizing guidelinesSizing decision tree

http://service.sap.com/quicksizingFree online tool to useBasis for hardware vendors’ sizings

http://www.sap.com/sizing

Thank You!

[email protected]

Sebastian Schmitt


© 2013 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.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP 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 other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.


© 2013 SAP AG. Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige der von der SAP AG und ihren Distributoren vermarkteten Softwareprodukte enthalten proprietäre Softwarekomponenten anderer Softwareanbieter.

Produkte können länderspezifische Unterschiede aufweisen.

Die vorliegenden Unterlagen werden von der SAP AG und ihren Konzernunternehmen („SAP-Konzern“) bereitgestellt und dienen ausschließlich zu Informationszwecken. Der SAP-Konzern übernimmt keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation. Der SAP-Konzern steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren.

SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und verschiedenen anderen Ländern weltweit. Weitere Hinweise und Informationen zumMarkenrecht finden Sie unter http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark.

011000358700000723482010 e

Documents

Transcript of 011000358700000723482010 e