75
Sebastian Schmitt, William Adams Performance & Scalability TEC111 Sizing and Hardware Capacity P SAP BusinessObjects and SAP Planning with Examples from P NetWeaver 7.30

Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

Embed Size (px)

DESCRIPTION

Tec111 Sizing and Hardware

Citation preview

Page 1: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

Sebastian Schmitt, William Adams Performance & Scalability

TEC111Sizing and Hardware Capacity Planning with Examples from SAP BusinessObjects and SAP Sizing and Hardware Capacity Planning with Examples from

and SAP NetWeaver 7.30

Page 2: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.

2

This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a

infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.

Page 3: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Agenda

Sizing Introduction and Basics

Sizing Tools and Results

Follow-On Activities and Sizing Tips

Demo Quick Sizer and Sizing examples

3

Page 4: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sizing Questions May Come in Different Flavors

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

“ 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“

4

Different Flavors

Definition Sizing

Translate business requirements into hardware requirements in an iterative process

questions / statementsCan 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 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

Page 5: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Some Key Performance Indicators

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

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

Disk sizeDisk I/O

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

Memory

Transferred amount of dataNetwork time and roundtripsCost factor: Leasing bandwidth

Front-endNetwork

Load

5

Some Key Performance Indicators

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 databaseStorage capacity

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

Page 6: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

** 6,000 dialog steps or 2,400 SAP transactions=̂

2,000 fully processed

order line items/hour**

Definition: SAPS

S APA pplicationP erformanceS tandard

Hardware-independent unit of measurement Sales & Distribution (SD) Standard Application BenchmarkMachine capacity is 100 SAPS when with the definition of the SD Standard Application Benchmark it can fully business process 2000 order line items per hour.Today servers with 4 processors, 40 cores and 80 threads deliver an average SAPS value of around 75.000 SAPS.

The power of hardware is measured in SAPS. It is a hardware independent unit to express the power of a certain machine (comparable to horsepower in cars).

SD Benchmark

6

2,400 SAP transactions

2,000 fully processed

order line items/hour**

100 SAPS

independent unit of measurement SAPS is derived from Sales & Distribution (SD) Standard Application BenchmarkMachine capacity is 100 SAPS when with the definition of the SD Standard Application Benchmark it can fully business process 2000 order line items per

Today servers with 4 processors, 40 cores and 80 threads deliver an average SAPS value of around 75.000 SAPS.

The power of hardware is measured in SAPS. It is a hardware independent unit to express the power of a certain machine (comparable to horsepower in cars).

Page 7: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

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

Upgrade Migration Business Units

Sizing takes place in different phases of a project

7

Different Times, Different Phases, Different Goals of Sizing

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

Realization Final Preparation

Going Live & Support

Business Units Functional Changes

GoLive

Sizing takes place in different phases of a project

Page 8: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Hardware Budget SizingSmaller companies

Very simple algorithmsAssumptions, likelihoodsLevel setting of projectRisk identification

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

Possible Definitions for Different Types of Sizing

Initial Sizings

All projectsSAP system monitorsGoal: Extend an existing system by load– E.g. by volume

100 additional users who'll do the same as the current productive ones

All projectsSAP system monitorsGoal: Extend an existing system by functions– By different functions, e.g. you are

live with CRM and want to add SCM

Re-Sizing Delta Sizing

Productive Sizings

Advanced Sizing

8

Expert Sizing

Questionnaires, formulas

Focus on core business processes

Large or complex projectsAdditional guidelinesCustom calculationsAnalysis of custom coding Custom sizing guidelines

Possible Definitions for Different Types of Sizing

Sizings

Goal: Extend an existing system by

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

All projectsSAP system monitorsSAP NotesGoal: Upgrade SAP software

Delta Sizing Upgrade Sizing

Sizings

GoLiveAdvanced Sizing

Page 9: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Some Factors That Influence Sizing

ParameterizationInterfacesSecurity settingsUnicodeA2A, B2B scenario

HW Platform Processor technologyDisk technologyNetwork technologySystem infrastructure

Avoiding dataArchiving strategiesInformation Lifecycle Management

Data VolumeTime for volume processingBackground processing, parallel jobsReporting

SAP SoftwareReleaseOLTP or OLAPIndustry solutions

Custom Coding, 3rd Party

Performance impactScalabilityBusiness process design

Technology PartnerResponsibility ofCustomer profile

9

Some Factors That Influence Sizing

System SettingsParameterizationInterfacesSecurity settingsUnicodeA2A, B2B scenario

Set up of business processesOrganizational structuresBusiness process design

Customizing

User BehaviorConcurrencyLAN/WANInternet/intranetActivity, e.g.

*-SearchEfficient navigation

Avoiding dataArchiving strategiesInformation Lifecycle Management

Disk Growth

CustomerSAP

Customer profile

Customer profile

Page 10: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Three-Party Collaboration Model

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

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

Hardware Vendors

SAP

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

Three parties collaborate in the benchmarking and sizing process

10

Expectations from benchmarking and sizing

Optimal performanceSuggestion for hardware configuration

Contributions Response time requirementsThroughput requirementsProvides business data input

Development and provision of benchmark

Regression testing for new releasesStandard sizing guidelines as part of quality

Sizing verification processes

Customer

SAP

Sizing Recommendation

(GB)Disk I/O operations per secFrontend bandwidth mbps

Three parties collaborate in the benchmarking and sizing process

Page 11: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Universally Applicable Statements on Sizing

20% of the transactions and scenarios create 80% of the load”Reliable sizings can only be done with

Scalable application softwareScalable hardwareMeaningful and nearly complete volume throughput or active user information

”Sizing results in KPIs

CPUDisk sizeDisk I/O Main memoryFront-end bandwidth requirements

Landscaping and configuration are related, but separate tasks”

11

Universally Applicable Statements on Sizing

Page 12: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Application Software Must Be Scalable Dimensions and Effects of Scalability

12

Application Software Must Be Scalable Dimensions and Effects of Scalability

Page 13: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Ensuring Scalability With Performance Tests

Single User TestSmall test system (QA, development), one user

Volume TestEquivalent to multi-user test, stress test, load test, benchmark

Analyze & measurescalable behavior

13

Ensuring Scalability With Performance Tests – Approaches

Quality and implications of accesses to persistence layerLinear resource consumptionParallel processing mechanisms, load balancingMemory usage and memory leaksDisk requirementsFront-end network load

Analyze & measure

Performance predictionsfor high volume environment

Verify assumptions and ...

Page 14: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Evaluating Measurement Results

Make sure you define at least three measurement points per scenario Example: Scalability with the number of line items – three tests

Application CPU time and DB time grow linearly

0.0000

0.0200

0.0400

0.0600

0.0800

0.1000

0.1200

0.1400

0.1600

0.1800

0.2000

0 10 20 30

CPU

tim

e in

sec

onds

No. of line items14

Make sure you define at least three measurement points per scenario – the more, the betterthree tests

ApplicationDBTotal

40 50 60 70line items

Page 15: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Assemble-To-Order (ATO)Cross Application Time Sheet (CATS) Financial Accounting (FI)Human Resources - Payroll (HR)Materials Management (MM)Production Planning (PP)Sales and Distribution (SD)

SAP ERP

Business IntelligenceBusiness Information Warehouse (BW)Data Mart (BI-D)Mixed Load (BI-MXL)

Enterprise PortalEmployee Self-Service (EP-ESS)People-Centric CRM (EP-PCC)

SAP NetWeaver

Benchmarks

• Industry standard• CPU-driven• Used since 1991• Delivers SAPS• <1s response time

since 2009

• CPU • Memory

SAP server powerSAP system power

SAP Power Benchmarks • Power consumption• Based on SD benchmark

15

E-SellingInteraction Center (IC)

SAP Customer Relationship Management

SAP for Banking – Transaction Banking (TRBK)SAP for RetailSAP for Utilities - Customer Care & Service (ISU/CCS)

Industry Portfolios

Warehouse Management (WM) Advanced Planner and Optimizer (APO)Demand Planning (DP)Prod. Planning/Detailed Scheduling (PP/DS)Supply Network Planning (SNP)

SAP Supply Chain Management

Project System (PS)

SAP Product Lifecycle Management

• InMemoryComputing

• I/O• CPU• Memory

Page 16: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Example – Certification 2011021

16

Source: www.sap.com/benchmark

Page 17: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

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

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

17

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

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

Are very hard to predict: Make sure there is a verification

Make sizing measurements, if required

Page 18: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Agenda

Sizing Introduction and Basics

Sizing Tools and Results

Follow-On Activities and Sizing Tips

Demo Quick Sizer and Sizing examples

18

Page 19: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sizing Information Platform: http://service.sap.com/sizing

19

http://service.sap.com/sizing

GuidelinesGeneral proceduresApplication-specific

ToolsQuick SizerOthers

Training opportunities

Page 20: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Different Standard Sizing Methods and Tools

Initial Calculation MethodEducated guesses

T-Shirt SizingSimple algorithms with many assumptions

FormulasSimple or more complex

Questionnaire without formulasFor structured questions

Quick SizerBased on users and / orthroughput

20

Different Standard Sizing Methods and Tools

Page 21: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Quick Sizer, SAP’s Online Sizing Tool

CharacteristicsStructured sizing questionnairesInput for – Initial sizing– GoingLive CheckHardware vendor contact list

Scope Key applications from–––Sizing by users and/or by throughput

Facts & FiguresAvailable online since 1996Free of chargeAs of 2010:– ca. 450,000 projects – avg. 35,000 new projects per year– ca. 150,000 different users

21

, SAP’s Online Sizing Tool

Scope Key applications from– Business Suite– Industries– SAP NetWeaverSizing by users and/or by throughput

Page 22: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Design Guidelines: Two Methodologies of the Quick Sizer

UsersLow, medium, high activity Application componentsAssumptions for load on CPU and disk

Result Average CPUDisk sizeDisk I/OMemory

ScopeSufficient for small projects with low user numbersSome application do not require user sizing (e.g. Process Integration)

Quick Sizer

Business throughput

Considers time periods

Result

Scope

Sizing based on users

22

Design Guidelines: Two Methodologies of the Quick Sizer

Quick Sizer

Business throughput Actual objects/transactions/scenarios

Considers time periodsResidence timeAverage working dayPeak load time frame

ResultAverage and peak CPU Disk size and growthDisk I/OMemory

ScopeFor larger or complex projects

Sizing based on throughput

Page 23: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sizing Process for a Quick Sizing –

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

23

– Overview

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

Page 24: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

SAP SD Standard Application Benchmark Results

ExampleRequired from sizing 2,000 SAPS

24

SAP SD Standard Application Benchmark Results

Required from sizing 2,000 SAPS Display

certificate

Page 25: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Side Step: Single Computing Unit Performance

Message 1: Through parallelization computer systems are getting more powerful over time regarding throughput

Message 2: unit is increasing only slightly

Message 3: SAP applications become more sophisticated and more flexible and therefore can exploit available newest technologies

* Numbers are based on internal investigations and are calculated values

25

Side Step: Single Computing Unit Performance

Message 2: The performance of the single computing unit is increasing only slightly*

SAP applications become more sophisticated and more flexible and therefore can exploit available newest technologies

Numbers are based on internal investigations and are calculated values

Page 26: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Side Step: Single Computing Unit Performance

0

500

1000

1500

2000

2500

3000

1994 1996 1998 2000 2002 2004

Published Results for SD Benchmarks (Two-Tier)

Average central or DB server CPU speed (MHz)

SAPS

SAPS

26

Side Step: Single Computing Unit Performance

2006 2008 2010 2012

Tier)

Average central or DB server CPU speed (MHz)

Page 27: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

New Sizing KPI in Quick Sizer – Single Computing Unit Performance

There are some SAP applications that benefit from a good Single Computing Unit performanceIntroduction of new sizing KPI Single Computing Unit performance into Quick

SCU performance classes A, AA, and AAA

More information can be found in SAP note: 1501701

Class Description

A This SAP solution benefits from good SCU performance.

AA This SAP solution benefits from a very good SCU performance.

AAA This SAP solution benefits from an excellent SCU performance.

27

Single Computing Unit Performance

There are some SAP applications that benefit from a good Single Computing Unit performanceperformance into Quick Sizer

Page 28: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Agenda

Sizing Introduction and Basics

Sizing Tools and Results

Follow-On Activities and Sizing Tips

Demo Quick Sizer and Sizing examples

28

Page 29: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sandbox SystemGoal: evaluation of functionalityA few users, some master dataSolution: minimum requirements

Sizing Development, Test, Sandbox and Q/A Systems

Development SystemDevelopers on one or several technology stacks

Depends on application, size power users, consider memory requirementsRule of thumb: 20 developers on a 2-processor, dual core server

Minimal System Requirements SAP 2 CPU Cores4 GB RAM 20 GB Disk

29

Test SystemDedicated for functional and non-functional testing

Possibly load testingSize depends on usage– Size like production system or use minimum

requirements

Q/A SystemSimilar to production systemSize like production systemIn 3-tier environment, usually only one app server

Sizing Development, Test, Sandbox and Q/A Systems

Minimal System Requirements SAP NetWeaver 7.30

Page 30: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sizing vs. Landscaping, Tuning and Configuration

Standard, advanced, expertOverall sizing KPIs – SAPS, memory, DB space, disk I/O– By users, by throughputDistribution on servers/stacksDatabase/ABAP/Java/TREX/liveCache

ConfigurationRelease, enhancement package, support packageProcessor speed – clock rate for response time or throughputDatabase, operating system, ...Administration settings, customizing

Sizing result

30

Sizing vs. Landscaping, Tuning and Configuration – Examples

TuningParameter settingsOLAP vs. OLTP parameter settingsResponse time vs. throughput tuningNumber of server nodes, threadsNumber of parallel jobs

2-tier, 3-tier, multi-tierHardware type, server type, memory, storage subsystem...Production, test, QA, sandbox, ...Fail-over, Backup/recovery strategyVirtualization (adaptive computing, cloud)Multiple components on one server

Landscaping

Page 31: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sizing and Virtualization

But, in a virtualized environment….

sizing is very important and necessary…storage is normally addressed over network (shared resource)…the same amount of memory that was sized for a non…more hardware is initially needed (overhead through virtualization)…you should get in touch with your infrastructure provider to find the right landscaping strategy…

With virtualization you can realize cost savings because of load balancing and system/server consolidation.

31

storage is normally addressed over network (shared resource)

the same amount of memory that was sized for a non-virtualized landscape must be available

more hardware is initially needed (overhead through virtualization)

you should get in touch with your infrastructure provider to find the right landscaping strategy

With virtualization you can realize cost savings because of load balancing and system/server

Page 32: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Validation of Sizing Assumptions

SAP tools and methods (SAP)GoingLive Check by SAP support organization– Before go-live– Check of Quick Sizer and other specifications with available

hardware

Early Watch Alert– Contributors to load from statistical records– Database and DB tables size and growth– Part of Solution Manager

Vendor tools and methods (Partner) Hardware utilization information– Operating system

Database monitors

32

Load testing (Customer)

Miscellaneous (Customer)Do business figures fit to one another?– 10,000 users per day vs. 100 business documents

Monitor the usage closely and adapt strategy, if necessary

Volume confirmationTesting of interfaces, backup strategy, ...Tuning of system parameters– Response time tuning– Parallel job tuning

Optimal hardware utilization

Page 33: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

How To Make Sizing Measurements

Test Case

Test System

Single-User Tests

Multi-User Load Tests

80/20 rule, simulate user behavior or background processingRepresentative, reproducible

Text– Text

Stable, no transports, no virtualization mechanismsPower saving and performance optimization of the CPUs must be switched off

Adherence to basic performance requirements (e.g. accesses to DB, linear dependency,...) Scalability with the size of the input parameter(s), e.g. size of the object. Scalability is referred to the resource requirements, such as CPU time, memory and DB disk size

Especially for Java-based applications, or highTo check locking mechanisms, stability, etc.Hardware scalability, sizing verification

Business Application, Scenario, Transaction

Load tests are also possible

33

How To Make Sizing Measurements – A Bird’s Eye View

80/20 rule, simulate user behavior or background processing

Stable, no transports, no virtualization mechanismsPower saving and performance optimization of the CPUs must be switched off

Adherence to basic performance requirements (e.g. accesses to DB, linear dependency,...) Scalability with the size of the input parameter(s), e.g. size of the object. Scalability is referred to the resource requirements, such as CPU time, memory and DB disk size

based applications, or high-throughputTo check locking mechanisms, stability, etc.Hardware scalability, sizing verification

Page 34: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Database Disk Space and Disk I/ODisk space

Fine granular:– Number of inserts into tables during test– DDIC information on table and index width

(DB independent) multiply entriesCoarse– DB snapshot before and after the test

Disk I/O: Monitor activity on ST04

Which KPIs to Collect

CPU / Processing PowerCPU time per scenario or per interaction stepDetailed information

On applicationOn databaseBrowser rendering time, network time (only for response-time critical applications consider synchronous traffic only)

34

MemoryMemory is usually dominated by user contexts methods different for ABAP and Java

ABAP– User context (maximum over test case)– Memory in background jobs usually no issueJava– User session space, processing space, framework space

Frontend Network LoadTransferred amount of data

Average number of KB sent and received per interaction stepCalculate bandwidth

Number of (synchronous) roundtrips between client and server

Impact on response time

Page 35: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Examples of Sizing Calculations Based on Measurement Results

Example 3 – ThroughputA payroll run of 100,000 payroll periods takes 20 minutes on a single-processor, quad-core, dual-thread server. Deductions:– On a quad-processor, quad-core, dual-thread server with the

same processors, the run should take 5 minutes– On a quad-processor, quad-core, dual-thread server with the

same processors, 400,000 payroll periods could be processed in 20 minutes

Example 1 – CPU time per scenarioYou measure 4s for a scenario of 10 interaction steps. Deductions– 900 (3600s/4s) scenarios per hour, evenly distributed at 100%

server/core/thread utilization– 590 (900*.65) at 65% utilization

(SAP standard)– 590 scenarios (e.g. one per user per hour) net time, no

think time included

35

Examples of Sizing Calculations Based on Measurement Results

Example 2 – CPU time per interaction stepIn a 10-step scenario, each step takes 0.4s on average. Deductions– Assume think time of 30s between steps incl. system response

time– 120 interaction steps per user per hour (3600s/30s) 12

scenarios at 100% utilization– 48 CPU s per user per hour (12*4s)– 75 users (3600/48) at 100% 49 at 65% (continuous work)

Example 4 – Lock on central objectA central object (e.g. material in goods issue) is locked for 200 ms Maximum throughput is 5 goods issues per second or 18,000 goods issues per hour. Poss. considerations if you need higher throughput – faster processor– optimization of coding– changing the business process – ...

Page 36: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Production Sizings: General Procedure

Re-Sizing Delta SizingAll projects

SAP system monitorsGoal: Extend an existing system by load- E.g. by volume

100 additional users who'll do the same as the current productive ones

All projectsSAP system monitorsGoal: Extend an existing system by functions- By different functions, e.g. you

are live with CRM and want to add SCM

ProcedureMonitor CPU utilization, table growth, and memory use

Relate it to a meaningful business entity, such as the number of concurrent users or the number of active projects

Different procedures according to goalsRe-sizing: Add the load coming in through the additional users and projects causing the same load structure Delta sizing: Treat like a new sizing and add calculated loadUpgrade sizing: Determine additional requirements and add calculated load

Judge whether your current hardware is sufficient, or whether you may need to buy new hardware

36

Production Sizings: General Procedure

Upgrade SizingAll projects

SAP system monitorsSAP NotesGoal: Upgrade SAP software

Relate it to a meaningful business entity, such as the number of concurrent users or the number of active projects

sizing: Add the load coming in through the additional users and projects causing the same load structure

Upgrade sizing: Determine additional requirements and add calculated load

Judge whether your current hardware is sufficient, or whether you may need to buy new hardware

Page 37: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

How to Monitor Current Resource Utilization

Available monitorsDisk Analysis DB02, DB monitor of vendor

(DB Performance Tables & Indexes)CPU Analysis ST06, ST03N, STAD, ST03G

(Workload Analysis, Statistical Records, Global System Workload AnalysisUser Analysis ST07, STAD, ST03G

(Application Monitor, Statistical Records)Memory Analysis SM04, STAD, GCLOG

(User List, Statistical Records)Front-End Network Load STAD, ST03N, ST03G, httplog

(Statistical Records, Workload Analysis)

As a rule, 20% of the processes cause 80% of the loadAnalyze

Growth rate of 20 largest tablesAverage and peak CPU loadAverage and peak memory utilization

37

How to Monitor Current Resource Utilization

Workload Analysis, Statistical Records, Global System Workload Analysis)

As a rule, 20% of the processes cause 80% of the load

Page 38: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Standard Scenarios for Production A Mixture of Different Approaches

Initial-Sizing

Quick SizerProject Current

Workload

+ Upgrade Increase in %

+ Load Increase in %

Upgrade or load increase

38

Standard Scenarios for Production Sizings –

Current Workload

Current Workload

+ Quick SizerProject

+ Quick SizerProject

+ Upgrade Increase in %

+ Load Increase in %

New functions or load increase

Upgrade & new functions

Page 39: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Agenda

Sizing Introduction and Basics

Sizing Tools and Results

Follow-On Activities and Sizing Tips

Demo Quick Sizer and Sizing examplesQuick Sizer DemoSizing SAP NetWeaver 7.30Sizing SAP BusinessObjects BI 4.0

39

Page 40: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

DemoQuick Sizer from SAP - www.service.sap.com/quicksizerwww.service.sap.com/quicksizer

Page 41: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Structure of Quick Sizer

QuestionnaireHardware infrastructure (optional)Per solution / key capabilityNavigation

SolutionsKey capabilities

13

41

Hardware infrastructure

Per solution / key capability

Project-wide information

WorkdaysStatusOwnerMethodLinks to hardware vendorsDocumentationDisclaimer

2

Page 42: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Navigation – Search

The search is version dependent.

The program searches for your search string across the visible and invisible parts of Quick Sizer. The results are displayed in the navigation tree.

All result lines are marked with an information icon.

If the string is found in the visible parts, the search string result will be presented bold and enlarged.

If the search string is found in the invisible parts, the entire result line will be presented bold, enlarged, and in italics.

If a result only partially contains the search string, only the search string is marked bold and enlarged.

42

1The program searches for your search string across the

. The results are displayed in the

If the string is found in the visible parts, the search string

If the search string is found in the invisible parts, the entire result line will be

If a result only partially contains the search string, only the search string is

Page 43: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Navigation

To open a questionnaire, click on the text

Meaning of the icons:Green: questionnaire filled in, no errors Yellow: no entries in questionnaireRed: questionnaire filled in and contains errors– If errors, no results are calculated– If you open a project with errors on specific questionnaires, the

navigation show the key capabilities with errorsLight bulb: Current questionnaire

If you click on the arrow, the list is displayed:Links to sizing guidelines that are not included in Quick

43

If you open a project with errors on specific questionnaires, the

Links to sizing guidelines that are not included in Quick Sizer

1

Page 44: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Project Header Information

Functions in the project headerSaving of sizing data

There are two methods for saving your input data:– Manually, by using the save button and automatically, by navigating from one questionnaire to another or by calculating resul

Create print page for each pageCalculate resultSet project to ‘GoingLive’ and ‘Final’

Only active, if entries are made in this projectFeedback:

You can use this function to send us your feedback about the Quick automatically for every version on a regular basis.

Quick Sizer tool documentationDirect access to hardware vendors sizing informationDisclaimerChange the number of workdays per year

Influences CPU, memory, and I/O, default: 220 days

44

Manually, by using the save button and automatically, by navigating from one questionnaire to another or by calculating results

You can use this function to send us your feedback about the Quick Sizer tool anytime. Furthermore, this anonymous survey will be conducted

2

Page 45: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Details on Help and Online Documentation

Quick Sizer tool documentationGeneral documentation on Quick

How to fill in the questionnaireHelp per questionnaire

45

Details on Help and Online Documentation

tool documentationGeneral documentation on Quick Sizer

Page 46: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Structure of Sizing Questionnaires

3

46

Structure of Sizing Questionnaires

3a Questionnaire-wide information

3b User sizing

3c Throughput sizing

Page 47: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Details an Questionnaire-Wide Information

Changing average workday and peak timesDefault workday: 9-18, default peak: 12-13You can modify these entries at questionnaire level

The average workday entry will change for all average sizingsThe default peak will be changed for lines without entries and new lines

Check inputYou can check the questionnaire for entry errors

Use default valuesYou can reset to default values if you changed them before (e.g. for Portal)

Long textYou can choose between long and short text. If you choose long text besides the abbreviation for the sizing element, also a displayed. This adjustment will be kept if you change the questionnaire.

Clear questionnaireYou can clear all information you entered on a questionnaire by using this button

LinkHow to fill in the questionnaire

47

Wide Information

You can choose between long and short text. If you choose long text besides the abbreviation for the sizing element, also a longer short text for the sizing element is

3a

Page 48: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Input Questionnaire: User-Based Sizing Tables

User sizing only considers concurrently active users

Most user sizings follow the standard pattern of low, medium, and high activity usersThink times between screen changes of 5 minutes, 30 seconds, and 10 seconds The usual distribution is 60-70% low, 30% medium, 5-10% highIf in doubt, take medium activity users

The user sizing result is independent of the throughput sizing result

Choose Clear to delete entries for marked lines

48

Based Sizing Tables

follow the standard pattern of low, medium, and high activity usersThink times between screen changes of 5 minutes, 30 seconds, and 10 seconds

10% high

The user sizing result is independent of the throughput sizing result

3b

Page 49: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Input Questionnaire: Throughput Sizing Tables

Entry fields / non-entry fields / mandatory input fieldsAll entry fields are whiteNon-entry fields are blue, non-entry check boxes are greyMandatory input fields are marked with a star ( * )

Functions in the input tablesTray: Optional trays are folded (for example on EWM questionnaires)Mark lines Insert and delete marked lines or clear the entries for marked lines

49

Input Questionnaire: Throughput Sizing Tables

Tray: Optional trays are folded (for example on EWM questionnaires)

Insert and delete marked lines or clear the entries for marked lines

3c

Page 50: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Description of Key Input Fields and Functions in the Throughput Sizing Tables

Element: To identify the sizing element. On mouse over will display the long text in detailCan be business object, entity, scenario, …

A/P - (A)verage or (P)eakDetermines if a sizing is an average sizing or a peak sizing Peak time is not for disk sizing and geared at determining the absolute top CPU,

memory, and I/O sizing

TI - Time intervalShows the chronological scope of the next field

(Y)ear: number of objects per yearPeak (P)eriod: Number of objects per defined time period(S)nap shot: Number of objects at anyone time

Objects - Number of objects Objects can be orders, projects, data records,…

Items Sub objects such as line items, WBS elements, key figures, … per object

50

Description of Key Input Fields and Functions in the Throughput

% chg / % dsp - changes & displays in %Number of changes and displays to an object in %. 1 change = 100%

Mon. = Months - Residence time in months

Arch. - Archiving project plannedNo influence on sizing result

S.t. / E.t - Begin and end of processing timesWorkday:

Can only be modified for entire questionnaireCannot be overwritten in input line

Peak period: Default can be changed for all empty lines Can be overwritten

ID - Identification For checks and calculations of (multiple) average(s) and/or peak(s)

Short text - Text field for comments

3c

Page 51: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sizing Results

51

ResultsRelease, depending on level (SAP solution, software component)

CPUCategorySAPS

MemoryMB

DiskCategoryGB (exception: statistics table MB)

I/OCategoryI/Os per second

Single Computing Unit Performance Classes A, AA, and AAA

Page 52: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Details on Result Display / Result Level

Result levelsProjectSAP solution (default, according to SAP solution)Software component (separately installable software)Key capabilitySizing element (for analysis on element level)Line results + inputs (e.g. for multiple averages / peaks)Results, statistics, inputs (includes statistics for documentation

52

Details on Result Display / Result Level

SAP solution (default, according to SAP solution)Software component (separately installable software)

Sizing element (for analysis on element level)Line results + inputs (e.g. for multiple averages / peaks)Results, statistics, inputs (includes statistics for documentation)

Page 53: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sizing Results – In Categories, SAPS, MB, and I/Os per second

The results are displayed both in categories and SAPS / disk value / I/Os per secondAt the result levels project, SAP solution, software component, and key capability, the results are rounded to

100 SAPS, 1 GB memory, and 1 GB disk

If your CPU sizing exceeds 48,000 SAPS or your disk sizing exceeds 1,6 TB or the I/O value is more than 18,000 I/Os per second, the Quick Sizer result should be handled with care.

Category Up to … SAPS Up to … GB

XS 2000 100S 8000 250M 16,000 500L 24,000 1000XL 36,000 1300XXL 48,000 1600XXXL Contact HW vendor or SAP

53

Categories, SAPS, MB, and I/Os per second

The results are displayed both in categories and SAPS / disk value / I/Os per secondAt the result levels project, SAP solution, software component, and key capability, the results are rounded to

If your CPU sizing exceeds 48,000 SAPS or your disk sizing exceeds 1,6 TB or the I/O value is more result should be handled with care.

Up to … I/Os per second

8003000600010,00014,00018,000

Page 54: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sizing Results – In Categories, SAPS, GB, and I/Os per second for SAP NetWeaver BW

For SAP NetWeaver Business Warehouse another logic is used, that means for SAP categories are calculated in a different way and other numbers are valid.

Category Up to … SAPS Up to … GB

XS 6000 500S 12000 1000M 24,000 2500L 36,000 5000XL 48,000 7500XXL 72,000 10,000XXXL Contact HW vendor or SAP

54

In Categories, SAPS, GB, and I/Os per second for

Business Warehouse another logic is used, that means for SAP NetWeaver BW the categories are calculated in a different way and other numbers are valid.

Up to … I/Os per second

20004000800012,00016,00024,000

Page 55: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Sizing Results – With Charts and Details Options

55

Charts and Details Options

Page 56: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Combined Result – Overview

Since version 22, Quick Sizer provides two different result approaches:

Classic approachCombined approach (new)

What’s included in the “old” classic approach?Two completely disjoint sizing results (user-based and throughput-based result)

What’s included in the combined approach?Total results of user-based and throughput-based sizings.

56

based and

Page 57: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Combined Result – Overview

Why did we include a new result approach?In the past, we had no information how to interpret the two disjoint results (user-based and throughput-based)It was not possible to calculate a total resultExample:– User-based sizing result for CRM is 25,000 SAPS– Throughput-based sizing for CRM result is also

25,000 SAPS– Is the total result the sum of both results?

57

Side remark:There are different sizings in the Quick Sizer:1. User-based sizings only 2. Throughput-based sizings only 3. User- and throughput-based sizings

But: In most of the cases, it’s a combination between user-based and throughput-based sizings

Page 58: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Classic and Combined Sizing Approaches

Classic approach• User-based and throughput-based sizing results are handled disjoint using this approach.

Combined approach• The new combined approach was introduced to calculate total results• Start with result level “sizing elements” (classic approach) - they are the basis to understand the calculation of the new

combined result. • They provide a very good possibility to check whether it exists a corresponding sizing element, or not.

58

Classic and Combined Sizing Approaches

based sizing results are handled disjoint using this approach.

total results. they are the basis to understand the calculation of the new

They provide a very good possibility to check whether it exists a corresponding sizing element, or not.

Page 59: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Agenda

Sizing Introduction and Basics

Sizing Tools and Results

Follow-On Activities and Sizing Tips

Demo Quick Sizer and Sizing examplesQuick Sizer DemoSizing SAP NetWeaver 7.30Sizing SAP BusinessObjects BI 4.0

59

Page 60: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Which Sizing Guidelines are Available?SAP NetWeaver 7.30

Usages Available SizingsSAP NetWeaver Process Integration 7.3

Part of Quick Sizer(www.service.sap.com/quicksizer)

SAP NetWeaver Portal 7.3 Part of Quick Sizer(www.service.sap.com/quicksizer)

SAP NetWeaver Business Process Management 7.3

Sizing Guideline available on the SAP Service Marketplace (www.service.sap.com/sizing)

SAP NetWeaver Business Warehouse 7.3

Part of Quick Sizer(www.service.sap.com/quicksizer)

60

Which Sizing Guidelines are Available?

Page 61: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

SAP NetWeaver PI 7.30

SAP PI is an integration platformfor SAP and non-SAP applicationsfor A2A and B2B scenariosfor a Service Oriented Architecturefor cross-component Business Process Management

61

Page 62: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

SAP NetWeaver PI 7.30: Overview on Input Interface

Message sizeNumber of messagesProcessing modeInbound AdapterOutbound AdapterIntegrated ScenarioccBPM complexityTime frame

62

PI 7.30: Overview on Input Interface

Page 63: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Run Greener with SAP NetWeaver Energy Saving Potential with SAP NetWeaver 7.3

SAP NetWeaver Process Integration 7.360% less energy (~32’000 kWh), 16 tons carbon/year*)Half the hardware required compared to dual stack deployment

SAP NetWeaver Portal 7.331% less energy (~13’000 kWh), 6.5 tons carbon/year*)Increased performance, smaller footprint

SAP NetWeaver Business Process Management 7.357% less energy (~24’000 kWh), 12 tons carbon/year*)Increased performance, smaller footprint

SAP NetWeaver Business Warehouse 7.310% less energy (~14’000 kWh), 7 tons carbon/year*)Increased performanceLower administrative effort

Energy saving potential compared to predecessor versions on same HW. Based on medium sized landscapeDetails on assumptions and calculation available from SAP on request

63

Run Greener with SAP NetWeaver Energy Saving Potential with SAP NetWeaver 7.3

Half the hardware required compared to dual stack deployment

landscape. Energy consumption savings for server and storage energy consumption.

Page 64: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Agenda

Sizing Introduction and Basics

Sizing Tools and Results

Follow-On Activities and Sizing Tips

Demo Quick Sizer and Sizing examplesQuick Sizer DemoSizing SAP NetWeaver 7.30Sizing SAP BusinessObjects BI 4.0

64

Page 65: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Introduction to the BusinessObjects BI SuiteOverview

The BI Suite is a collection of tools for …

Reporting and Analysis Dashboards Data Exploration

On a single BI Platform which provides …

Authentication and Security

A Common Semantic Layer

Report and document scheduling and delivery

65

Introduction to the BusinessObjects BI Suite

Reporting and Analysis Dashboards Data Exploration

Page 66: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Which Sizing Guidelines are Available? SAP BusinessObjects BI 4.0

Solution Available Sizings

Plans for the Future

SAP BusinessObjects Version BI 4.0 (SP0) Web Intelligence

Sizing Guideline on SAP Service Marketplace

It’s planned to include it into Quick Sizer

SAP BusinessObjects Version BI 4.0 (SP0) Analysis, edition for OLAP

Sizing Guideline on SAP Service Marketplace

It’s planned to include it into Quick Sizer

SAP BusinessObjects Version BI 4.0 (SP0) BI Workspace

Sizing Guideline on SAP Service Marketplace

It’s planned to include it into Quick Sizer

SAP BusinessObjects Version BI 4.0 (SP0) Dashboard Designer

Sizing Guideline on SAP Service Marketplace

It’s planned to include it into Quick Sizer

SAP BusinessObjects Crystal Reports Enterprise (SP0)

Sizing Guideline on SAP Service Marketplace

It’s planned to include it into Quick Sizer

Crystal Reports 2011 Sizing Guideline on SAP Service Marketplace

It’s planned to include it into Quick Sizer

Connection Server (CS) Sizing Guideline on SAP Service Marketplace

It’s planned to include it into Quick Sizer

66

Which Sizing Guidelines are Available?

for the

to include it into Quick

to include it into Quick

to include it into Quick

to include it into Quick

to include it into Quick

to include it into Quick

to include it into Quick

Page 67: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Introduction to the BusinessObjects BI SuiteWeb Intelligence

An end-to-end self-service experience covering a range of user types

Analysis capabilities combined with free-form report layout for authorsInteractivity on formatted reports gives casual users freedom answer their own questions [within a safe sandbox of trusted data

Broad access to data and contentSingle user experience for access to enterprise (relational and OLAP) and personal (Excel, Web Services) data sourcesSelf-service data mash-up for new insights across data silos

67

Introduction to the BusinessObjects BI Suite

service experience covering a range of

form report layout for

gives casual users freedom to a safe sandbox of trusted data]

Single user experience for access to enterprise (relational and Web Services) data sources

up for new insights across data silos

Page 68: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Initial Sizing GuidesThe Sizing Table, Tiers

Refer to the guides for more details

Size Users ApplicationTier SAPS

Processing Tier SAPS

Intelligence Tier SAPS

Application TierMemory

Processing Tier Memory

S … … … … … …

M … … … … … …

L … … … … … …

68

Refer to the guides for more details on the services in each tier

Intelligence TierBI Platform

Processing Tier / WebI, Crystal, …

Application Tier /WAS (Tomcat, etc.)Intelligence

Tier Memory

Page 69: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

T-shirt Sizing GuidesSample Scenario: Web Intelligence

An organization of 5,000 employees, would like to create a user account for everyone

500 users are expected to be logged-in at any point in time

Of the 500 users who are logged-in, will be actively “clicking away” simultaneously

This is only an example. Always see the most recent Sizing Guide or Quick Sizer for official sizing data.

Size Users SAPSAppl. Tier

SAPSProcess. Tier

Memory –Appl. Tier

Memory –Process.Tier

S … … … … …

M 50 7450 3380 8GB 8GB

L … … … … …

XL … … … … …

XXL … … … … …

8GB8GB7450 338050

50

69

An organization of 5,000 employees, would like to create a user account for everyone

in at any point in time

in, will be actively “clicking away” simultaneously

. Always see the most recent Sizing Guide or Quick Sizer for official sizing data.

Page 70: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Companion GuideTuning and deploying

Contains information on the architecture landscape, workflows, and settings used to obtain the T-Shirt sizing data in the guide

You can use this information to determine differences between your documents, user mix and landscape vs. the deployment used to generate the sizing guide data

Use it also to fine tune your BI4 platform for performance and scalability

This document is constantly enriched based on customer and field feedback

70

Contains information on the architecture landscape, Shirt sizing

You can use this information to determine differences between your documents, user mix and landscape vs. the

Use it also to fine tune your BI4 platform for performance

This document is constantly enriched based on customer

Page 71: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

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 developmentSAP offers different tools for different products

71

Sizing means translating business requirements into hardware requirementsThe sizing process (and thus the sizing result) is closely tied to the lifecycle of the software

The success of the sizing exercise almost entirely depends on the quality of the data

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

Page 72: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 SAP AG. All rights reserved.

Further Information

SAP Public Web:SAP Developer Network (SDN): http://www.sdn.sap.com/irj/sdn/performanceSAP Service Marketplace (SMP: https://www.service.sap.com/sizingSAP Website: http://www.sap.com/benchmark

Related SAP Education and Certification Opportunitieshttp://www.sap.com/education/

Related Workshops/Lectures at SAP TechEdBI206 – SAP BusinessObjects Business Intelligence 4.0 Performance and Sizing Best Practices, lecture (1 hour)

72

http://www.sdn.sap.com/irj/sdn/performance-analysishttps://www.service.sap.com/sizing

Related SAP Education and Certification Opportunities

TechEd 2011Business Intelligence 4.0 Performance and Sizing Best

Page 73: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

Feedback – TEC111Please complete your session evaluation.Be courteous — deposit your trash, and do not take the handouts for the following session.

TEC111Please complete your session evaluation.

and do not take the handouts for the following session.

Page 74: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

Thank You!Contact information:

Sebastian SchmittT +49 6227 [email protected]

Page 75: Tec111 Sizing and Hardware Capacity Planning With Examples From BO and Netweaver 7.30

© 2011 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.Oracle and Java are registered trademarks of Oracle and/or its affiliates.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

© 2011 SAP AG. All rights reserved.

75

2011 SAP AG. All rights reserved.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.