Académique Documents
Professionnel Documents
Culture Documents
Contents
1 Introduction
.........................................3
of Throughput Sizing........................... 23
Book ......................................................5
Conclusion ..........................................24
2 Sizing Methods
......................................7
3.5 Conclusion................................................. 27
Expert Sizing....................................... 10
Standard Tools Even for Experts.......11
30
Sizings.................................................... 13
Resizing.............................................. 13
Categories.......................................... 31
3 Sizing Approaches
5 Quick Sizer
................................17
..............................................35
Creating a Project............................... 36
Approaches.................................................. 20
Initial Page.......................................... 41
User-Based Sizing................................ 21
Contents
Questionnaires ....................................43
... 51
77
9 Sizing Details
........................................79
Model ..........................................................79
.................................59
Services................................................ 80
Measurements ....................................60
Requirements).................................... 86
Mode ...............................................61
Benchmark Results.............................. 88
Check ..................................................68
Test System......................................... 95
on the Measurements......................... 98
.....................101
Processes ..............................................75
............103
..........................105
Index
........................................................107
2 Sizing Methods
the
sales orders and sales order items are much more
critical to CPU sizing since they represent transaction data. In terms of revenue, an average of 2,000
sales orders per day is quite considerable; however,
from the point of view of software, this is not a high
throughput volume . SAP has several customers who
process more than a million sales order items per day.
depends
closely
on
the
amount
of
informational
value of the sizing project
the
different phases. In addition, you should note that
not
all the phases described in Table 2.1 have to occur in
an
sizing). Moreover, we are using several custom developments. How should we carry out a sizing
SAP project.
Thus, if the system GoLive is still way down the
road
project?
with
component in
accounting and is therefore more detailed.
Perhaps this customer has already carried
www.sap-press.com 7
further
analyzing
these
kinds
of
(see Table
2.1). The
2 Sizing Methods
Phase
Point in Time
Description
Orientation phase
(Phase A)
18 to 12 months
prior to GoLive
You familiarize yourself with the software functionality and want to know what the range
of expenses is for the new hardware. Accordingly, you will certainly know which processes
you want to map using the software, and you also know the approximate amount of data
that is supposed to be processed. However, you are not familiar with the SAP jargon, nor
are you interested in specifi c releases.
The fi rst business blueprints have been created, and now you need reliable information on
the scope of hardware you have to order because you must make sure you meet all your
deadlines. You know how to implement the relevant processes, have become more familiar
with SAP products and SAP terminology, and know which release you want to use.
Implementation phase
(Phase C)
6 to 0 months
prior to GoLive
You have ordered the hardware or are just about to do so, and you want to be absolutely
sure that sizing is correct. For example, you are able to measure core processes using the
performance monitors.
Consolidation phase
(Phase D)
System is
operational
The system is operational and is supposed to be consolidated. Region 1, for instance, has
gone live with a specifi c software, and Region 2 is now supposed to go live on the same
system.
Extension phase
(Phase E)
System is
operational
The system is operational and you want to add new functions. For example, your live system runs the SAP ERP applications, and you want to add CRM applications now.
Upgrade phase
(Phase F)
System is
operational
The system is operational and you want to perform an upgrade. For example, the system
runs on SAP R/3 Enterprise and you want to upgrade it to SAP ERP 6.0.
Table 2.1
likelihoods
Advanced Sizing
Medium
to
Large
Companies
_
Throughput estimates
Questionnaires,
formulas
Risk identification
Usage
of
Expert Sizing
Live Go-
Large/Complex Projects
_
Additional guidelines
Custom calculations
standard
tools
Initial Sizings
Resizing
All Projects
All Projects
_
Upgrade Sizing
Delta Sizing
All Projects
_
SAP Notes
(see
Section 4.2,
T-shirt Sizing), which have the advantage of
requiring you
to answer only a few questions. Of course, the
disadvan-
(server)
with
two
processors,
www.sap-press.com 9
2 Sizing Methods
locks
an
object
and
can
become
performance bottleneck
because all other requests have to wait
would then have to pay (in the above example)
an additional $15,000
released again.
- $20,000
for a
correspond-
for
is able to map
since the
implementation
of
new
production
break
quality
assurance
systems
and
testing
landscapes.
down
the
complex
business
Advanced Sizing
If youre in a situation in which theres a high risk
of misjudging
the
requirements
by
several
100
percents, you
should refi ne your budget sizing by using what is
referred
to as advanced sizing. For example, if the range of
CPU
power youre dealing with is between 8 and 16
cores, a
more detailed sizing makes a lot of sense because
it pro-
CPU sizing in
that it distinguishes between the average
CPU utilization
(average sizing) and the utilization at peak
times (peak sizing):
For processor requirements, you can
perform an
average sizing in such a way that you
specify the
number of objects that are processed
per year as well
In
most
cases,
expert
sizing
and
and
analyses.
We
can
roughly
the
sizing
tools
full
utilization
of
you
have
identifi
ed
business
transactions as
being close to the standard, you can use Quick
Sizer (see
Chapter 5). That is, you can use Quick Sizer for
partial
sizings.
Another option for using Quick Sizer in expert
sizing is that you can use it for optimizing process
fl ows from the point of view of sizing. For
example, if you use overlapping, performance-critical process chains, you can
use the 24-hour load profi le provided by Quick
Sizer to ascertain whether it is possible to perform
moves (see also Section 5.3, Average and Peak
Sizing). Quick Sizer enables you to map and
document additional loads which, for example,
extension
made in the customer system, the same
process
that was mapped in Quick Sizer now needs
Simplifi ed Example of Expert Sizing
more
resources.
enter sales
ERP
llment and
such
the ERP
Quick
www.sap-press.com 11
2 Sizing Methods
about
the locking procedure or memory
requirements.
In the sizing environment, load tests
have a hybrid
nature: On the one hand, you can use
them as a siz-
use them to
verify sizing results. Because customers
usually use
load test .
nd detailed
Single-user Analysis
Tests.
simple
principle: As soon as integration tests can be
performed (i.e., when business processes can be
functionally mapped in a system), you use the
standard
performance monitors of the SAP system to
measure the CPU time , memory consumption, or
database growth on your hard disk, depending on
your requirements. You can then use this data
in a rule of three to create the sizing forecast.
Table
2.2
provides
an
overview
of
the
procedure to
be applied in a single-user analysis, from defi
ning an
appropriate test case to applying the customerspecifi c sizing rule. Chapter 6, Performance
Monitors
information
and
Traces,
on
contains
sizing-based
detailed
performance
measurements.
Step
Description
Table 2.2
Load Test
Load tests are occasionally used in the context
of
expert sizings and make sense when a single-user
analysis does not provide suffi cient information
12
The advantages of expert sizing over other sizing methods are found in the higher degree of accuracy and reliability of the information. If you manage a sizing project
for a complex or large customer, you should defi nitely
consider aspects from expert sizing, even though the collection and analysis of the information takes more time.
could
look as follows: You want to add another 200
named
users to the 1,567 existing ones. We assume that
the
ratio between named users and active users is
identical
www.sap-press.com 13
of the
two application
servers is 56%.
Database
213GB out of 512GB are occupied with
a monthly growth of 7GB.
Memory
26GB out of 32GB are being consumed.
By using a system monitor, the customer
has found
out that approximately
1,254 named
users out of a
total of 1,567 have been active during the
period analyzed. Based on this information, you can
now determine whether the existing hardware is
suffi cient or whether it must be extended.
Resizing
A basic prerequisite for resizing is that only
the throughput and user volumes can change, but not
the functionality. Based on the current load situation
and the new information, you can easily
determine future requirements using a rule of three.
Typical
resizings
consolidations
phased rollouts,
occur
in
system
or in what is referred to as
in which customers install
2 Sizing Methods
there
is
one
special
follow-
ing calculations:
Active Users
The ratio between 200 and 1,567 is 12%,
which means that the number of active
users will prob-
in Section 9.2,
SAP Application
Performance
Standard,
each hardware
confi guration in the SAP environment has
servers
can absorb a
utilization of
62.7% quite well. However, many customers
plan
a target utilization of 30% to 50% for the
application servers, which is why an extension is at
least conceivable here.
Main Memory
26GB (out of 32): 26GB 1.12 ~= 29GB
29GB out of 32GB of allocated memory
might be
a bit tight. It is therefore advisable to
extend the
memory.
Database Space
7GB of growth corresponds to 7GB 1.12 =
8GB per month
Currently, 312GB out of 512GB are being
used. If
the database grows by 96GB (8GB 12
months)
per year, bottlenecks can occur in a very
short
time. Thus, the disk space should be extended.
Delta Sizing
Because delta sizing can be performed only when
new functions are added to an existing software
application, the procedure is similar to that of
initial sizing, the only difference being that the
2.4 Summary
ing the main memory. The best thing to do is to calculate a best case and a worst case.
Memory (Best Case)
26GB (out of 32): 26GB 1.05 ~= 27.3GB
Memory (Worst Case)
26GB 30% = 33.8GB
Probably, the future memory requirement will be
within that range.
settings are
changed as well. All this can have an impact on the
number of work processes, buffer settings, or other
things.1
Upgrade sizing refers to the additional
requirements
of SAP software. SAP uses regression tests to check
the
resource consumption of the most important
transactions
and to create a delta. This information is made
available
to all customers in SAP Notes, such as SAP Note
901070,
which describes the resource consumption
between
SAP ERP Core Component (SAP ECC) 5.0 and SAP
ERP
6.0. The SAP Notes provide information about the
delta
regarding the number of database calls, CPU
requirements, memory requirements, and database space.
Because these SAP Notes provide standardized
information about different transactions, they carry the
risk of
you currently using a transaction that is
counterbalanced
by other transactions.
Sample Upgrade Sizing
A (fi ctitious) SAP Note on delta resource
consumption
states that the resource consumption in the
memory
increases by 5% on average. Transactions A and
F do
not show any additional consumption, whereas
Transaction G consumes an additional 30%. The CPU
you want
to extend the processing power of application
servers,
you can add more servers, replace the CPU , or add
Single-Instance Projects
From the point of view of sizing, the majority
of singleinstance projects in which companies change
from a bestof-breed strategy2 to a single-instance strategy
(one software
vendor,
all
data
in
one
system)
more
CPUs, depending on your specifi c production model.
However, a new application server affects the
databases memory requirements because it involves
the
addition of new database users. A higher volume
generally means an increase in read and write activities,
which,
in turn, may have an impact on the disk subsystem.
2 In a best-of-breed strategy, you always choose the
product from the best vendor for each (technological) area.
The
different products are then connected with each other
via
interfaces.
and
American
systems
Consequently, this
means the following:
If the SAP software has different release
versions,
an upgrade sizing must be performed fi
rst. The relevant factors will be upgraded so that all
systems
have the same version.
The next step involves resizing the SAP
software
based on the same release version; that
is, the current
consumptions
of
existing
SAP
systems must
be analyzed and totaled.
Finally, a delta sizing must be performed
for the
legacy
software.
Ultimately,
the
2.4 Summary
Because SAP software shows a high degree of
scalability, you can consider a linear change in
consumption as
a given fact. The same applies to hardware: If
www.sap-press.com 15
2 Sizing Methods
Index
2-tier implementation 47
3-tier implementation 47
80/20 rule 35
Concurrent user 21
Consolidation phase 8
Core 18
Core process
Active user 21
Advanced sizing 10
Analysis
of customer data 11
performance monitor 51
transaction design 60
Application server
Accelerator
Business
Intelligence
Data Dictionary 58
Delta sizing 13, 14
Blueprint phase 8
Business Intelligence Accelerator
(BI
Disk space
database 14, 39, 47
DPU
Accelerator) 18
(DPU)
Dual-stack installation 26
C
Computing
Center
Management
System (CCMS)
Chief Information Officer (CIO) 4, 74
Chief Process Innovation Officer (CPIO)
4
Coding
custom 11, 59, 62
per second 39
IAS
International
Accounting
Standard
(IAS)
Implementation
2-tier 47
3-tier 47
Implementation phase 8, 71, 76
Implementation project
27, 71,
74
Initial sizing 8, 63, 75
Input error 41, 43
International
Cache 27
CCMS
Disk growth 53
35, 42,
71
I/O (input/output)
Disclaimer 42
Accelerator
Hardware vendor
Hardware costs 4, 71
4,
D
Database monitor 53
Baseline test 62
BI
CPU utilization 13
Archiving object 45
55 Application team 73
analyzing 11
G
GLC
Customer data
54 Application profile 71
Custom development 8
Core team 73
CPU load 24
of customer processes 11
Extension phase 8
Accounting
Standard
(IAS)
33
Employee Self-Services 75
Evaluation phase 74
EWC
IT team 73
Expressiveness
Java-based
of sizing project 7
application 25, 47
Java Virtual Machine (JVM) 57
www.sap-press.com 107
Index
K
Key performance indicator 12, 17, 31
Physical memory 18
Processor 18
Sizing
Product availability 5
approach 17
by throughput 22
Landscaping 6, 72, 78
by users 4, 20
Programming guidelines 30
definition 3
Project team 73
expressiveness 7
Latency 19
liveCache 18
analysis 60
informational value 31
initial 8
Quick Sizer 35
multi-user mode 61
methods
performing 61
object 45
design principles 35
toolkit 24
principle 3
tools 60
Local area network (LAN)
production 8, 51, 63
functions 36, 40
17,
production sizing 13
navigation 41
73 Logged-on user 21
result 40, 46
scope 20
throughput-based
Maximum
Extended
Memory
Transaction 57
Memory consumption 13
Memory requirement 40, 52, 56,
57 Methods 7
user-based 20, 38
Save function 41
in
verification 59, 63
Sizing project 71
application team 73
Reference database 23
definition 72
core team 73
reference installations 23
documentation 74, 77
Minimum requirement 5
execution 71, 74
goal 74
planning 71
procedure 74
Network load 19
Network traffic 32
project scope 71
SAP
Non-disclosure policy 23
Application
success factors 71
Standard
O
Offline questionnaire 33
Processing
29
Operating system monitor 52
Orientation phase 8
Software
31 Status 42
System consolidation
Check
System integration 65
15, 63, 68
21, 40,
58
Product Availability Matrix
Performance
analysis
SAPS 40
Peak sizing 49
(ST30)
12 Performance monitor 51
51,
57 Phased rollout 13
Phases
of sizing projects 7
Standard
Application
Benchmarks
23
Scalability 3, 61
Sessions 21
Single-instance project 15
Single-user analysis 12
T-shirt sizing 9, 30
Target utilization 14, 50
Portal 21, 44
Process Integration 4
13,
SAP NetWeaver
architecture
Business Intelligence
PAM
stakeholders 72
Performance
Analytical
IT team 73
Rule of thumb 29
Named user 20
38,
result 38
7, 8, 11, 16,
27 measurement 12
planning 59
Online
formula 32
Index
Transaction ST05 57
active 21
Transaction ST06 52
concurrent 21
Transaction ST07 54
Transaction STAD 56
logged-on 21
named 20
Upgrade phase 8
Upgrade sizing
75 Usage type 47
User
Verification 77
of sizings 59, 63
W
Wide area network (WAN)
17,
73 Work days
in Quick Sizer 42
www.sap-press.com 109