Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
38Activity
0 of .
Results for:
No results containing your search query
P. 1
Sap Sizing Example

Sap Sizing Example

Ratings: (0)|Views: 991|Likes:
Published by Chai Choon Keet

More info:

Published by: Chai Choon Keet on Jun 30, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

11/15/2012

pdf

text

original

 
www.sap-press.com
 
1
Sizing SAP
®
Systems
Susanne Janssen, Ulrich Marquard
Contents1 Introduction
................................................. 3
Sizing Definition
.................................... 3
The Sizing Principle
................................ 3
Business Management and Technology
4
Goals of This Book
................................. 4
Target Group and Structure of theBook
....................................................... 5
Related Topics
........................................ 5
2 Sizing Methods
........................................... 7
2.1 Phases of Sizing Projects
................................... 7
2.2 Methods for Initial Sizings
................................ 8
Hardware Budget Sizings
....................... 8
Advanced Sizing
..................................... 10
Expert Sizing
.......................................... 10
Standard Tools — Even for Experts
....... 11
Analyzing Customer Data
...................... 11
2.3 Sizings Based on Productive Customer Data
.... 12
Basic Analysis for All ProductionSizings
.................................................... 13
Resizing
.................................................. 13
Delta Sizing
............................................ 14
Upgrade Sizing
....................................... 15
Single-Instance Projects
......................... 15
2.4 Summary
........................................................... 15
3 Sizing Approaches
..................................... 17
3.1 Factors That Influence Sizing
............................ 17
3.2 Key Performance Indicators
.............................. 18
3.3 Overview of Different SizingApproaches
....................................................... 20
Sizing by Users
....................................... 20
Advantages and Disadvantages of User-Based Sizing
.................................. 21
Sizing by Throughput
............................. 22
Basic Considerations and Assumptionsfor Throughput Sizing
............................ 23
Advantages and Disadvantagesof Throughput Sizing
............................. 23
Sizing by Reference Installations
........... 23
Sizing by Load Tests
............................... 24
Conclusion
............................................. 24
3.4 User and Throughput Sizing Models
................. 24
Calculating CPU Requirements
............. 24
Calculating Memory Requirements
....... 25
Calculating Disk Requirements
.............. 26
Frontend Network Requirements
......... 27
Conclusion for These Approaches
......... 27
3.5 Conclusion
........................................................ 27
4 Sizing Tools
................................................... 29
4.1 Rule of Thumb/Reality Check
........................... 29
Bottom-Up Method
.............................. 30
Top-Down Method
................................ 30
4.2 T-shirt Sizing
...................................................... 30
Categories
.............................................. 31
Pros and Cons
........................................ 31
4.3 Sizing Formula
................................................... 32
4.4 Offline Questionnaire
....................................... 33
4.5 Summary
........................................................... 33
5 Quick Sizer
................................................... 35
5.1 Quick Sizer Projects
.......................................... 36
Creating a Project
.................................. 36
Filling Out Sizing Questionnaires
.......... 37
Determining the Sizing Result
............... 38
5.2 Functions
........................................................... 40
Initial Page
............................................. 41
Navigation Tree
...................................... 41
Header Bar
............................................. 41
 
2
© Galileo Press 2007. All rights reserved.
Contents
Questionnaires
....................................... 43
Results Page
........................................... 45
5.3 Average and Peak Sizing
.................................... 48
5.4 Summary
........................................................... 50
6 Performance Monitors and Traces
...... 51
6.1 Operating System Monitor
............................... 52
6.2 Database Monitor
............................................. 53
6.3 Application Monitor
.......................................... 54
6.4 Single Record Statistics
.................................... 56
6.5 Performance Trace
............................................. 57
6.6 Summary
........................................................... 58
7 Sizing Verification
...................................... 59
7.1 Load Tests
.......................................................... 59
Phase 0: Preparation
.............................. 59
Phase 1: Performing IndividualMeasurements
....................................... 60
Phase 2: Analyzing the TransactionDesign in Single Mode
.......................... 60
Phase 3: Load Tests in Multi-UserMode
..................................................... 61
7.2 Verification via Support Services
....................... 63
SAP GoingLive Check
............................ 63
SAP EarlyWatch Check
.......................... 67
SAP GoingLive Functional UpgradeCheck
..................................................... 68
7.3 Summary
........................................................... 69
8 Executing Sizing Projects
........................ 71
8.1 Before the Sizing Project Begins
....................... 71
Chicken or the Egg?
............................... 71
Project Scope
......................................... 71
Stakeholders in a Sizing Project
............. 72
Definition of a Sizing Project
................. 72
8.2 Project Team
...................................................... 73
8.3 Methodical Procedure
...................................... 74
Step 1: Define Project Contents andGoals
...................................................... 74
Step 2: Determine Performance-CriticalProcesses
................................................ 75
Step 3: Decide on the Approaches andMethods to Be Used
.............................. 75
Step 4: Define Milestones and Preparea Detailed Schedule
............................... 76
Step 5: Acquire Information and Applythe Methods
.......................................... 76
Step 6: Analyze First Results and Adaptthe Methods
.......................................... 77
Step 7: Consolidate the Results andGet Confirmation from Stakeholders
.... 77
8.4 Summary
........................................................... 78
9 Sizing Details
............................................... 79
9.1 Basic Foundations of the SAP SizingModel
................................................................ 79
SAP Software Architecture
.................... 79
Application Services and DatabaseServices
.................................................. 80
Modeling CPU Consumption
................ 81
Allocating Sufficient Memory(or: Modeling Physical Memory)
........... 84
Allocating Sufficient Disk I/OCapabilities (or: Modeling Disk I/ORequirements)
....................................... 86
Modeling Network Bandwidth
.............. 86
Measuring Resource Consumption
....... 88
Benchmark Results
................................ 88
Results from a Java Benchmark
............. 90
9.2 SAP Application Performance Standard
............ 92
9.3 Performing Sizing Measurements
..................... 94
Step 1: Define the Test Case
................. 94
Step 2: Identify the Test System
............ 95
Step 3: Create the Test Case in theTest System
............................................ 95
Step 4: Measure the Sizing KPIs
............ 96
Step 5: Create Sizing Guidelines Basedon the Measurements
........................... 98
9.4 Summary
........................................................... 99
10 Summary and Outlook
............................ 101
A Frequently Asked Questions
................. 103
A.1 Sizing Approaches
............................................. 103
A.2 Quick Sizer
........................................................ 104
A.3 Sizing Projects
................................................... 104
B Literature and Links
.................................. 105
Index
............................................................... 107
 
www.sap-press.com
 
7
2 Sizing Methods
Sizing projects are carried out at very different stages of an SAP project. They represent an iterative process thatdepends closely on the amount of information that isavailable to you at a certain point in time to make reliablestatements on the actual hardware requirements.Accordingly, in each sizing project, you will often facenew situations that you must react to with different meth-ods and, consequently, using different tools. This chapterfocuses on these different methods.
2.1 Phases of Sizing Projects
SAP regularly receives information requests like the fol-lowing:
“We
 
are
 
a
 
large
 
customer
 
in
 
the
 
consumer
 
 goods
 
indus-try
 
with
 
30,000
 
business
 
 partners
 
and
 
60,000
 
 sales
 
orders
 
containing
 
50
 
line
 
items
 
 per
 
month.
 
How
 
much
 
hardware
 
do
 
we
 
need
 
 for
 
our
 
SAP
 
application?”
This is a rather general question. The customer needsinformation about hardware for a first estimate. Thequestion itself does not indicate why this is a largecustomer. Perhaps the customer is only looking for apartial solution since the volumes mentioned indicatethat this customer is a large medium-sized company.The business partners represent master data and arenot yet relevant to sizing because they do not gener-ate any load during live operation. In contrast, thesales orders and sales order items are much morecritical to CPU sizing since they represent transac-tion data. In terms of revenue, an average of 2,000sales orders per day is quite considerable; however,from the point of view of software, this is not a highthroughput volume. SAP has several customers whoprocess more than a million sales order items per day.
“We
 
can’t
 
 find
 
any
 
 guidelines
 
 for
 
the
 
FIN-FSCM-TRN
 
component
 
in
 
 your
 
 sizing
 
area
 
http://service.sap.com/
sizing
 ).
 
 Moreover,
 
we
 
are
 
using
 
 several
 
custom
 
develop-ments.
 
How
 
 should
 
we
 
carry
 
out
 
a
 
 sizing
 
 project?”
This question refers to a specific component inaccounting and is therefore more detailed. Perhapsthis customer has already carried out sizing projectsfor other SAP applications and wants to performanother one for this particular application. In addi-tion, the customer wants to know how sizing can bedone for proprietary developments.
“We
 
are
 
 planning
 
to
 
consolidate
 
our
 
 seven
 
data
 
centers
 
into
 
one.
 
Can
 
we
 
 simply
 
add
 
up
 
existing
 
 sizings?”
This question (which comes from an existing SAPcustomer) refers to a system consolidation processin which additional hardware requirements must betaken into account if the different existing systemsare combined. System consolidation and
 single-instance
 
concepts
, which are used to check whetherall systems can be globally integrated with one data-base, are currently red-hot issues with our customers.
“We
 
are
 
currently
 
running
 
Release
 
SAP
 
R/3
 
4.6C 
 
and
 
want
 
to
 
upgrade
 
to
 
SAP
 
ERP
 
6.0.
 
What
 
are
 
the
 
upgrade
 
 factors?”
This customer uses a specific release that he wantsto upgrade across multiple releases in one step andtherefore wants to know if new hardware needs to bepurchased for that.By further analyzing these kinds of requests, we ulti-mately get to the different phases in which you can per-form sizing projects (see Table 2.1). The informationalvalue of the sizing project can vary, depending on thedifferent phases. In addition, you should note that notall the phases described in Table 2.1 have to occur in anSAP project.Thus, if the system GoLive is still way down the roadand you — as a customer — are not yet very familiar with

Activity (38)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Rafa Marenco liked this
psreddy liked this
John O'Neill liked this
mushahidur liked this
ehtesham11 liked this
shivakumara_V liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->