sap sizing

7/24/2019 SAP Sizing

1/25

Sizing SAPSystems

Susanne Janssen, Ulrich Marquard

Contents

1 Introduction ......................................... !asic Considerations and Assum"tionsSizing #e$ nition................................... %or &hrough"ut Sizing.........................'

&he Sizing Princi"le ................................ Ad(antages and #isad(antages

!usiness Management and &echnology ) o% &hrough"ut Sizing...........................'

*oals o% &his !oo+ .................................) Sizing y -e%erence Installations..........'&arget *rou" and Structure o% the Sizing y oad &ests .............................')

!oo+....................................................../ Conclusion ..........................................')

-elated &o"ics......................................../ .) User and &hrough"ut Sizing Models .............')

Calculating CPU -equirements........... .')

' Sizing Methods ......................................0 Calculating Memory -equirements .... '/'.1 Phases o% Sizing Proects.................................0 Calculating #is+ -equirements ...........'2

'.' Methods %or Initial Sizings..............................3 4rontend 5et6or+ -equirements... .....'0

7ard6are !udget Sizings ......................3 Conclusion %or &hese A""roaches .......'0

Ad(anced Sizing ..................................18 ./ Conclusion.................................................'0

9:"ert Sizing.......................................18

Standard &ools ; 9(en %or 9:"erts..... ..11 ) Sizing &ools.............................................'shirt Sizing................................................8

-esizing..............................................1 Categories..........................................1

#elta Sizing .........................................1) Pros and Cons ......................................1

U"grade Sizing ....................................1/ ). Sizing 4ormula ...............................................'

Single>Instance Proects ......................1/ ).) ?@ ine uestionnaire...................................

'.) Summary ......................................................1/ )./ Summary ......................................................

Sizing A""roaches ................................10 / uic+ Sizer ............................................../.1 4actors &hat InB uence Sizing.........................10 /.1 uic+ Sizer Proects......................................2

.' ey Per%ormance Indicators ..........................13 Creating a Proect...............................2

. ?(er(ie6 o% #iDerent Sizing 4illing ?ut Sizing uestionnaires..... ....0

A""roaches..................................................'8 #etermining the Sizing -esult ............3

Sizing y Users ....................................'8 /.' 4unctions .....................................................)8

Ad(antages and #isad(antages o% Initial Page..........................................)1

User>!ased Sizing................................'1 5a(igation &ree ....................................)1

Sizing y &hrough"ut ..........................'' 7eader !ar ..........................................)1

666.sa">"ress.com 1
http://www.sap-press.com/http://www.sap-press.com/


2/25

Contents

uestionnaires ....................................) Ste" /E Acquire In%ormation and A""ly

-esults Page ...........................................)/ the Methods .......................................02

/. A(erage and Pea+ Sizing................................)3 Ste" 2E Analyze 4irst -esults and Ada"t

/.) Summary ....................................................../8 the Methods .......................................00

Ste" 0E Consolidate the -esults and2 Per%ormance Monitors and &races ... /1 *et Con$ rmation %rom Sta+eholders 00

2.1 ?"erating System Monitor.........................../' 3.) Summary ......................................................03

2.' #ataase Monitor ........................................./

2. A""lication Monitor.................................../) < Sizing #etails ........................................0

lo6ingE

e are a large customer in the consumer goods

indus>

try 6ith 8,888 usiness "artners and 28,888

sales

orders containing /8 line items "er month. 7o6

much

hard6are do 6e need %or our SAP a""licationKN

&his is a rather general question. &he customer

needs

in%ormation aout hard6are %or a $ rst estimate.

&he

question itsel% does not indicate 6hy this is a

large

customer. Perha"s the customer is only loo+ing

%or a

"artial solution since the (olumes mentioned

indicate

that this customer is a large medium>sized

com"any.

&he usiness "artners re"resent master data and

arenot yet rele(ant to sizing ecause they do not

gener>

ate any load during li(e o"eration. In contrast,

the

sales orders and sales order items are much more

critical to CPU sizing since they re"resent transac>

tion data. In terms o% re(enue, an a(erage o% ',888sales orders "er day is quite consideraleO ho6e(er,

%rom the "oint o% (ie6 o% so%t6are, this is not a high

through"ut (olume . SAP has se(eral customers 6ho

"rocess more than a million sales order items "er da

e cant $ nd any guidelines %or the 4I5>4SCM>&-5

com"onent in your sizing area Hhtt"E==ser(ice.sa".co


4/25

zing. Moreo(er, 6e are using se(eral custom de(elo">

ents. 7o6 should 6e carry out a sizing

oectKN

is question re%ers to a s"eci$ c

m"onent in

counting and is there%ore more detailed.

rha"s this customer has already carried

t sizing "roects %or other SAP

"lications and 6ants to "er%orm another

e %or this "articular a""lication. In addi>

on, the customer 6ants to +no6 ho6

zing can e done %or "ro"rietary

(elo"ments.

e are "lanning to consolidate our se(enta centers

to one. Can 6e sim"ly add u" e:isting

zingsKN

is question H6hich comes %rom an e:isting

AP

stomer re%ers to a system consolidation

ocess

6hich additional hard6are requirements

ust e

+en into account i% the diDerent e:isting

stems

e comined. System consolidation and

ngle>

stance conce"ts, 6hich are used to chec+

hether

systems can e gloally integrated 6ith

e data>

se, are currently red>hot issues 6ith our

stomers.

e are currently running -elease SAP -=

2C andant to u"grade to SAP 9-P 2.8. hat are

e u"grade

ctorsKN

is customer uses a s"eci$ c release that he

ants to u"grade across multi"le releases in

e ste" and there%ore 6ants to +no6 i%

6 hard6are needs to e "urchased %or

at.

%urther analyzing these +inds o%

ests, 6e ulti>ely get to the diDerent "hases in 6hich

can "er>

sizing "roects Hsee &ale '.1. &he

in%ormational

(alue o% the sizing "roect can (ary, de"ending on

the

diDerent "hases. In addition, you should note that

not

all the "hases descried in &ale '.1 ha(e to occur in

an

SAP "roect.

&hus, i% the system *oi(e is still 6ay do6n the

road

and you ; as a customer ; are not yet (ery %amiliar6ith

666.sa">"ress.com0


5/25

' Sizing Methods

Phase Point in &ime #escri"tion

?rientation "hase 13 to 1' months Qou %amiliarize yoursel% 6ith the so%t6are %unctionality and 6ant to +no6 6hat the range

HPhase A "rior to *oi(e o% e:"enses is %or the ne6 hard6are. Accordingly, you 6ill certainly +no6 6hich "rocesses

you 6ant to ma" using the so%t6are, and you also +no6 the a""ro:imate amount o% data

that is su""osed to e "rocessed. 7o6e(er, you are not %amiliar 6ith the SAP argon, nor

are you interested in s"eci$ c releases.

!lue"rint "hase HPhase ! 1' to 2 months &he $ rst usiness lue"rints ha(e een created, and no6 you need reliale in%ormation on

"rior to *oi(e the sco"e o% hard6are you ha(e to order ecause you must ma+e sure you meet all your

deadlines. Qou +no6 ho6 to im"lement the rele(ant "rocesses, ha(e ecome more %amiliar

6ith SAP "roducts and SAP terminology, and +no6 6hich release you 6ant to use.

Im"lementation "hase 2 to 8 months Qou ha(e ordered the hard6are or are ust aout to do so, and you 6ant to e asolutely

HPhase C "rior to *oi(e sure that sizing is correct. 4or e:am"le, you are ale to measure core "rocesses using the

"er%ormance monitors.

Consolidation "hase System is &he system is o"erational and is su""osed to e consolidated. -egion 1, %or instance, has

HPhase # o"erational gone li(e 6ith a s"eci$ c so%t6are, and -egion ' is no6 su""osed to go li(e on the same

system.

9:tension "hase System is &he system is o"erational and you 6ant to add ne6 %unctions. 4or e:am"le, your li(e sys>

HPhase 9I o"erational tem runs the SAP 9-P a""lications, and you 6ant to add C-M a""lications no6.

U"grade "hase System is &he system is o"erational and you 6ant to "er%orm an u"grade. 4or e:am"le, the system

HPhase 4 o"erational runs on SAP -= 9nter"rise and you 6ant to u"grade it to SAP 9-P 2.8.

&ale '.1 Phases in hich Sizing Can !e Per%ormed

the so%t6are, you 6ill "roaly ha(e only asicin%orma>

tion on ho6 you are going to use it so that you

can at least ma+e a rough estimate o% the costs

in(ol(ed. #uring the course o% the im"lementation

"roect, you can re$ ne your initial assum"tions y

using standard sizing rules in order to ta+e a closer

loo+ at the critical issues.

I% an installations com"le:ity diDers too much

%rom

the standard, you can, %or instance, measure

customer

"rocesses in order to create customer>s"eci$ c

sizings.

All these diDerent "hases require diDerent sizing

meth>

ods. In this conte:t, 6e generally distinguish

et6een ini>

tial and "roduction sizings . 4igure '.1 "ro(ides an

o(er>

(ie6 o% the a(ailale sizing methods, 6ith initial

sizings

eing sho6n in the u""er section and

"roduction siz>

ings in the lo6er one. 9:"ert sizing is mar+ed as a

hyrid

ecause under certain circumstances, some"rocesses can

e ma""ed using standard methods 6hile, at the

same

time, customer>s"eci$ c data can e

analyzed.

&he %ollo6ing sections descrie the

characteristics o%

these diDerent sizings in greater detai

At this "oint it is

im"ortant to +no6 that sizings can e

"er%ormed 6ithinse(eral "hases o% a "roectE Sizing is an

iterati(e "rocess.

!udget sizing, %or e:am"le, could e

done in "hases A

and !, ad(anced sizings in "hases A

through C, e:"ert siz>

3 L *alileo Press '880. All rights reser(ed.


6/25

n "hases ! and C, resizings in "hase #, delta sizings

ase 9, and u"grade sizings in "hase 4.

Methods %or Initial Sizings

l sizings are sizings that re%er to ne6 installations,

is, installations in 6hich you use SAP so%t6are %or

$ rst time. &hat is also the case i%, %or instance, you

to use SAP S-M %or the $ rst time 6hile SAP 9-P

eady running in your com"anys "roduction system

least the sizing %or SAP S-M 6ill e considered as

g initial.

e"ending on the "roect "hases, 6e diDerentiate ini>

sizings into hard6are udget sizings Hudget sizings %or

t, ad(anced sizings, and e:"ert sizings. Usually, udget

gs and ad(anced sizings are ased on tools, 6hereas

rt sizings are a mi:ture o% tools and addi>

l rules or measurements.

6are !udget Sizings

main characteristic o% udget sizings is that they

t require much in%ormation %rom the customer and

contain many assum"tions Hi.e., (alues "ro(ided y

ased on e:"erience. 4or e:am"le, i% the only in%or>


7/25

'.' Methods %or Initial Sizing

7ard6are !udget Sizing

Smaller Com"anies

RFery sim"le algorithms

R Assum"tions,

li+elihoods

Re(el setting o% "roect

R-is+ identi$cation

Initial Sizings

-esizing

All Proects

RSAP system monitors

R *oalE 9:tend an e:isting system

y load He.g., y (olume, 188additional users 6ho 6ill dothesame as the current"roducti(eones

Post *oi(e Sizings

Ad(anced Sizing

Medium to arge

Com"anies

R&hrough"ut estimates

R uestionnaires,

%ormulas

R Usage o% standard

tools

R4ocus on core usiness

"rocesses

#elta Sizing

All Proects


R *oalE 9:tend an e:istingsystem

y %unctions Hy diDerent%unctions, e.g., you are li(e6ith C-M and 6ant to addSCM

9:"ert Sizing i(e *o>

arge=Com"le: Proects

RAdditional guidelines

RCustom calculations

RAnalysis o% custom coding

RCustom sizing guidelines

U"grade Sizing

All Proects


RSAP 5otes

R*oalE U"grade SAP so%t6are

4igure '.1 ?(er(ie6 o% Sizing A""roaches and Methods

1

mation you ha(e is that 188 users 6ill use SAP C-M,ut

you dont +no6 the other a""lications they 6ill

use and

6hat 6ill e their a(erage acti(ity, you can

certainly "er>

%orm the sizing, ut in the long run, the

in%ormational

(alue "ro(ided y the result o% the sizing "rocess

6ill e

too restricted.

4or this reason, udget sizings are usually"er%ormed 6ay ahead o% the *oi(e "hase

Hmost o% the time in Phase A i% the goal is to

estimate the a""ro:imate sco"e o% hard6are.

4or udget sizings, you can use the user>ased

sizing

%unction in SAPs uic+ Sizer Hsee Cha"ter /, uic+

Sizer.

Alternati(ely, you can use &>shirt sizings Hsee

Section ).',

&>shirt Sizing, 6hich ha(e the ad(antage o%

requiring you

to ans6er only a %e6 questions. ?% course, the

disad(an>

tage is that the rough categorization into S through

"ro(ides only limited in%ormational (alue. ?ccasionalsuch sizings can e suG cient, de"ending on the s"eci$

situation.

4or this reason, it ma+es a lot o% sense to com"are

time and eDort you 6ant to in(est into a sizing "ro

6ith the "otential hard6are costs.


8/25

dget Sizings 7el" in 9stimating the 9ntire Size

s su""ose a udget sizing determines

88 SAPS

P A""lication Per%ormance Standard1.

rently,

88 SAPS corres"ond more or less to a

l>core

chine Hser(er 6ith t6o "rocessors,

ch has a list

ce o% T1/,888. 5o6 you can ma+e u"

r mind

ether it ma+es sense to tac+le a rather

nsi(e siz>

"rocess or 6hether you 6ant to ta+e

e o% the %ollo6ing t6o ris+sE

-esult Is &oo 7igh

&his means the ser(er 6ill not e %ully

tilized dur>

ng li(e o"erations. A result that is too

igh o%ten

ccurs ecause the initial estimates are

sually too

onser(ati(e.

-esult Is &oo o6

&his means that you must uy additional

ard>

6are. In this case, the question is

6hether you can

Dord to use the 6rong assum"tions.

ets su">

ose your initial estimate is 6rong y88. Qou

See Section


9/25

' Sizing Methods

6ould then ha(e to "ay Hin the ao(e e:am"le

an additional T1/,888 > T'8,888 %or a

corres"ond>

ingly igger ser(er. &here are some customers

%or6hom e:"enses in this range are critical,

since the

im"lementation o% a ne6 "roduction

ser(er also in(ol(es the "urchase o% ne6

quality assurance systems and testing

landsca"es.

Ad(anced Sizing

I% youre in a situation in 6hich theres a high ris+

o% mis>udging the requirements y se(eral 188

"ercents, you

should re$ ne your udget sizing y using 6hat is

re%erred

to as ad(anced sizing. 4or e:am"le, i% the range o%

CPU

"o6er youre dealing 6ith is et6een 3 and 12

cores, a

more detailed sizing ma+es a lot o% sense ecause

it "ro>

(ides a higher degree o% reliaility. &o do that, you

can use

additional %unctions o% uic+ Sizer, such as its

through>

"ut>ased %unctionality, 6hich allo6s you to

determine

the CPU load on a(erage as 6ell as y "ea+ load Hsee

Sec>

tion /., A(erage and Pea+ Sizing.

Usually, ad(anced sizing occurs in "hases ! and

C. Inthese "hases, the $ rst usiness lue"rints ha(e

already

een created so that im"ortant and sizing>rele(ant

in%or>

mation aout the usiness so%t6are a""lications is

a(ail>

ale to you. &his in%ormation could include, %or

instance,

a PC (endors decision aout 6hich im"ortant

materi>

als are im"erati(e that an a(ailaility chec+ e

"er%ormed

%or H"rocessors, %or e:am"le. An a(ailaility chec+

loc+s

an oect and can ecome

"er%ormance ottlenec+

ecause all other requests ha(e to 6

until the oect is

released again.

&hus, in an ad(anced sizing "roc

you %ocus more

on the core usiness "rocesses . uic+ Sis ale to ma"

the +ey "rocesses o% the SAP !usin

Suite and tries to

rea+ do6n the com"le: usin

scenarios into the most

im"ortant transactions and oects

addition, uic+

Sizer "ro(ides the o"tion to $ ne>tune

CPU sizing in

that it distinguishes et6een the a(er

CPU utilization

Ha(erage sizing and the utilization at "

times H"ea+ siz>

ingE

4or "rocessor requirements, you can

"er%orm an

a(erage sizing in such a 6ay that yo

s"eci%y the

numer o% oects that are "rocesse

"er year as 6ell



10/25

the size o% these oects. I% you ha(e times o% "ea+

ad, you can, o% course, s"eci%y them.

rough"ut>ased sizing enales you to determine

greater detail in 6hich areas and at 6hat time

e CPU "ea+ load occurs H%or e:am"le, in the 6ee+

%ore Christmas or 5e6 Qears. 9s"ecially 6ith

gard to ac+ground>oriented "rocesses such as

ose rele(ant to controlling or year>end settlements,

s in%ormation is critical and cannot e ta+en care

y user>ased sizing.

dra6ac+ o% ad(anced sizing is that you ha(e to

iarize yoursel% 6ith the core usiness "rocesses in

r to otain the a""ro"riate in%ormation %rom the

de"artments %or the uic+ Sizer questionnaire. &his

ainly ta+es more time than as+ing %or the numer o%

s Has is done, %or instance, in a udget sizing "rocess, ut it

uch more accurate.ote that ad(anced sizing is still a tool>ased "rocess.

N category in uic+ Sizer re"resents a large cat>

y in the tool>controlled area, ut not necessarily in

ntire sizing conte:t. 4or e:am"le, in uic+ Sizer, the

st category HN starts at 8,888 SAPS. A numer

rge customers o"erate on )8,888 to 188,888 SAPSO

6 other customers o"erate in the range o% 88,888

and higher.

rt Sizing

anges o% 8,888 SAPS and higher, SAP there%ore rec>

mends that its customers not rely e:clusi(ely on one

g tool ut rather that they analyze the core "rocesses

ao(e all, the customer "rocesses in great detail (ia

rt sizing.

is method is "articularly suited %or com"le: usi>

transactions, in>house de(elo"ments, and large>

e installations. Com"le: usiness transactions may also

r in smaller installations, such as in the su""ly chain or

tailing systems. *loal installations, 6hich are not only

ned y their size, are also eligile can>tes %or e:"ert sizing ecause o% the time diDerences that

t e ta+en into account.

e ale to "er%orm an e:"ert sizing "rocess, you must

E


11/25

'.' Methods %or Initial Sizing

Identi$ ed all "rocesses that are critical %or "er%or>

mance.

Used standard tools %or the core "rocesses.

#etermined the "er%ormance>critical areas in

6hich your "rocesses de(iate %rom thestandard.

9:"ert sizings are "er%ormed ust e%ore the

system *oi(e, that is, 6hen the %unctionality has

een clearly de$ ned and "erha"s e(en een

im"lemented. In most cases, e:"ert sizing

re"resents an iteration on a "re(i>

ously "er%ormed udget or ad(anced sizing so

that you can use the data o% these "re(ious

"rocesses as a asis and sim"li%y it, i% necessary.

!asically, this method consists, on the onehand, o% a mi:ture o% standard sizing and

"er%ormance tools, and on the other, o% additional

"rocedures and analyses. e can roughly

sudi(ide these t6o "arts intoE

&he %ull utilization o% the sizing tools

%unctionality Hin "articular, uic+ Sizers so that

they meet s"eci$ c requirements at least in

"art.

&he analysis and "er%ormance monitoring o%

core "rocesses in the customer system.

&he %ollo6ing sections "ro(ide an o(er(ie6 o% ho6

you can use standard tools in e:"ert sizing to

otain use%ul in%ormation, at least aout "arts o%

your system.

Standard &ools ; 9(en %or 9:"erts

hene(er you ha(e identi$ ed usiness

transactions as

eing close to the standard, you can use uic+

Sizer HseeCha"ter /. &hat is, you can use uic+ Sizer %or

"artial

sizings.

Another o"tion %or using uic+ Sizer in e:"ert

sizing is that you can use it %or o"timizing "rocess

B o6s %rom the "oint o% (ie6 o% sizing. 4or

e:am"le, i% you use o(erla">

"ing, "er%ormance>critical "rocess chains, you can

use the ')>hour load "ro$ le "ro(ided y uic+

Sizer to ascertain 6hether it is "ossile to "er%orm

mo(es Hsee also Section /., A(erage and Pea+

Sizing. uic+ Sizer enales you to ma" and

document additional loads 6hich, %or e:am"le,

ha(e een caused y custom coding .


12/25

"li$ ed 9:am"le o% 9:"ert Sizing

om"any uses SAP C-M a""lications to

er sales

ers and uses SAP 9-P %or sales order %ul$

ent and

&he sales order "rocessing %unctions in

9-Ptem ha(e een custom>coded.

or this reason, a mi:ed a""roach is used

:"ert

ng in such a 6ay that core "rocesses are

""ed

ough the standard as much as "ossile,

le the

er "rocesses are a""roached ste" y

"E

irst the com"any uses uic+ Sizer to

ate a

tandard sizing %or sales order entry in

P C-M.

!ecause the sales orders that ha(e een

ered

n the C-M system are %urther "rocessed

he

9-P system, a certain amount o% e:tra

acity is

dded to the sending system, that is,

P C-M,ccording to the corres"onding sizing

s.

&he sizing o% SAP 9-P is ma""ed in uic+

er on

he asis o% the total numer o% orders.

%act

hat the orders are trans%erred through

nter>

ace does not negati(ely aDect the

%ormance

o% the 9-P system Hon the contrary, it

, rather,

"ositi(e eDect ecause there is no user

rac>

ion. &his sizing re"resents the asic

cture o%

he 9-P sizing.

!ecause the com"any does not +no6 u"

ront

6hat the im"act o% e:tending the sales

rder "ro>

essing 6ill e, it "er%orms "er%ormance

measure>

ments that sho6 that, ecause o% the

e:tension

made in the customer system, the same

"rocess

that 6as ma""ed in uic+ Sizer no6 needs

more

resources.

&he customer is no6 ale to increase the

9-P

result %or sales order "rocessing y 8 in

such

a 6ay that the customer multi"lies theuic+

Sizer result y a %actor o% 1.. ?ther results

H%or instance, in 7- are not aDected y this.

Analyzing Customer #ata

?ne o% the most im"ortant tas+s o% e:"ert sizing

consists

o% analyzing s"eci$ c customer "rocesses . &y"ical

cases in

6hich it ma+es sense to analyze the "er%ormance $gures

on the asis o% custom data ecause o% the strong

inher>

ent customer>s"eci$ c nature include the %ollo6ingE

666.sa">"ress.com11


13/25

' Sizing Methods

Fariant con$ guration that e(aluates com"le:oect

de"endenciesE Its runtime can hardly e

antici"ated in the standard, i% at all.

9ach custom e:tension.

&o analyze customer data, the %ollo6ing t6o

methods are a(ailaleE single>user analysis and the

load test .

Single>user Analysis

Single>user analysis is ased on a relati(ely

sim"le

"rinci"leE As soon as integration tests can e

"er>

%ormed Hi.e., 6hen usiness "rocesses can e

%unc>tionally ma""ed in a system, you use the

standard

"er%ormance monitors o% the SAP system to

mea>

sure the CPU time , memory consum"tion, or

data>

ase gro6th on your hard dis+, de"ending on

your requirements. Qou can then use this data

in a rule o% three to create the sizing %orecast.

&ale '.' "ro(ides an o(er(ie6 o% the

"rocedure to

e a""lied in a single>user analysis, %rom de$

ning an

a""ro"riate test case to a""lying the customer>

s"e>

ci$ c sizing rule. Cha"ter 2, Per%ormance

Monitors and &races, contains detailed

in%ormation on sizing>ased "er%ormance

measurements.

Ste" #escri"tion

1 #e$ ne test case

' Identi%y test system

Create test case in test system

) Measure sizing PIs

/ Im"lement measurement results in sizing method

2 A""ly sizing rule

&ale '.' Ste"s in Creating a Sizing -ule

oad &est

oad tests are occasionally used in the conte:t

o%e:"ert sizings and ma+e sense 6hen a single>user

analysis does not "ro(ide suG cient in%ormation

aout

the loc+ing "rocedure or memory

requirements.

In the sizing en(ironment, load tests

ha(e a hyrid

natureE ?n the one hand, you can us

them as a siz>

ing tool. ?n the other hand, you can

use them to(eri%y sizing results. !ecause custom

usually use

them to (eri%y sizing results, you can

nd detailed

in%ormation on them in Section 0.1,

&ests.

1' L *alileo Press '880. All rights reser(ed.


14/25

ng Measurement Fersus Per%ormance Analysis

e that sizing measurements reB ect only the actual

tus. !ased on sizing measurements, you can deter>

ne 6hether a usiness transaction is scalale. In

conte:t, scalaility means that the resource con>

m"tion increases linearly 6ith the numer or size

he "rocessed "roects. I% a "rocess is not scalale,must analyze and resol(e the "rolem in a "er%or>

nce su"roect.

ad(antages o% e:"ert sizing o(er other sizing meth>

are %ound in the higher degree o% accuracy and reli>

y o% the in%ormation. I% you manage a sizing "roect

com"le: or large customer, you should de$ nitely

der as"ects %rom e:"ert sizing, e(en though the col>

on and analysis o% the in%ormation ta+es more time.

Sizings !ased on Producti(e Customer

#ata

g is an iterati(e "rocess ; that is, e(en o"erational

llations can e suect to change "rocesses that

t the resource requirements, as the %ollo6ing e:am>

6ill sho6E

u 6ant to consolidate your e:isting system land>

a"e H%or e:am"le, y merging all your international

sidiaries on one ser(er.

u 6ant to add additional %unctions to an e:isting system

or e:am"le, y installing a C-M system on a ser(er that

ready hosts an 9-P system.

u 6ant to u"grade -elease to -elease Q.

hese situations can aDect the hard6are and require a

e or less com"rehensi(e sizing "roect. &he maor

ntage o% sizings that are ased on a "roduction sys>

is that you can use your o6n data and settings as a

. In other 6ords, you do not need to rely on assum">

made y SAP.egarding "roduction sizings , 6e distinguish et6een

ollo6ing three methods, 6hich "ursue diDerent

sE

esizing

a resizing "roect, the through"ut or user (olume


15/25

'. Sizings !ased on Producti(e Customer #a

changes, ut not the "rocesses Hor customizingor

"arameter settings, and so on.

#elta Sizing

In a delta sizing "roect, you add ne6

%unctionality. U"grade Sizing

An u"grade sizing in(ol(es a change o% the

SAP release.

Common to all these sizing methods is that you

must $ rst analyze the status o% the e:isting

system e%ore you can "lan the ne6 hard6are

requirements.

Production System Sizings Fersus uic+ Sizer

&he uneatale ad(antage o% sizing on the asis

o% "ro>

duction data is that you can ta+e your o6n

data, "ro>

cesses, and settings into account. uic+ Sizer has

een

designed %or ne6 installations and contains

assum">

tions aout the "roducti(e o"eration. 4or this

reason,

6e recommend uic+ Sizer %or initial sizings only.

!asic Analysis %or All Production Sizings

4or all "roduction sizings, you must $ rst identi%y

the uti>

lization o% the sizing>rele(ant com"onents in the

e:ist>

ing system. Using the a""ro"riate monitors,

6hich are descried in detail in Cha"ter 2, you

can determine the %ollo6ing in%ormationE

CPU Utilization

hat is the actual utilization o% the CPUK Can

the e:isting hard6are com"ensate %or the %uture

loadK 7ere, you must distinguish et6een the

utilization o% the a""lication ser(er and that in

the dataase.

Memory Consum"tion

7o6 much room %or maneu(er do you ha(e

regard>

ing the memory requirementE ill it increase

or stay the sameK

#ataase S"ace

&a+e a loo+ at the 8 iggest tales and inde:es,and ma+e a noteE 7o6 quic+ly did they gro6

during the last se(eral monthsK

?nce you ha(e determined the current utilization or t

dataase gro6th and the increasing memory requir

ments using the (arious (endor>s"eci$ c monitors or t

SAP monitors, you should relate this in%ormation to

sim"le usiness +ey $ gure. Usually this is the users,


16/25

n also e "roects or calls. Alternati(ely, you can also

the numer o% acti(ities or sales orders,

nding, on the one hand, on 6hich unit is

suited to reB ect the res"ecti(e usiness

ity, ut also, on the other, on ho6 easily it

e determined.

m"le Analysis o% a Production System

%ollo6ing e:am"le %orms the asis %or

descri">

n o% indi(idual sizing methods. A

tomer uses

tegic "rocurement in the S-M

ironment. &he

lysis o% the current utilization "ro(ides

%ollo6>

resultE

CPUUtilization o% the dataase ser(er is

)O that o% the t6o a""lication

er(ers is /2.

#ataase

1*! out o% /1'*! are occu"ied 6ith

monthly gro6th o% 0*!.

Memory

2*! out o% '*! are eing consumed.

using a system monitor, the customer

%ound

that a""ro:imately 1,'/) named

rs out o% a

al o% 1,/20 ha(e een acti(e during the

od ana>

ed. !ased on this in%ormation, you can

6 deter>

ne 6hether the e:isting hard6are is

G cient or 6hether it must e e:tended.

zing

sic "rerequisite %or resizing is that onlyhrough>

and user (olumes can change, ut not

unction>

!ased on the current load situation

the ne6 in%ormation, you can easily

rmine %uture require>

ts using a rule o% three.

"ical resizings occur in system

olidations or in 6hat is re%erred to as

ed rollouts, in 6hich customers install

so%t6are in diDerent "hases in their

ness units or international susidiaries.

izing a Production System

!ased on the ao(e e:am"le Hsee "re(ious o:,

Sam>

"le Analysis o% a Production System, a resizing

could

loo+ as %ollo6sE Qou 6ant to add another '88

named

users to the 1,/20 e:isting ones. e assume that

the

ratio et6een named users and acti(e users is

identical

666.sa">"ress.com1


17/25

' Sizing Methods

among the ne6 users and that they 6ill do thesame

as the e:isting users, so that 6e can ma+e the

%ollo6>

ing calculationsEActi(e Users

&he ratio et6een '88 and 1,/20 is 1',

6hich means that the numer o% acti(e

users 6ill "ro>

aly increase y 1'.

CPU #ataase Ser(er

) V 1' corres"onds to ) W 1.1' X

3.1 A utilization o% 3 is suG cient %or a

dataase ser(er. Many customers "lan a

target utilization o% '/ to /8 %or the

dataase ser(er.

CPU A""lication Ser(er

/2 V 1' corres"onds to /2 W 1.1' X

2'.0

&he a""lication ser(ers can asor a

utilization o%

2'.0 quite 6ell. 7o6e(er, many customers

"lan

a target utilization o% 8 to /8 %or the

a""lica>

tion ser(ers, 6hich is 6hy an e:tension is at

least concei(ale here.

Main Memory

'2*! Hout o% 'E '2*! W 1.1' YX '

zation o% 2/. As 6e 6ill demonstrin Section


18/25

e, 6hich can e s"eci$ ed y the hard6are (endors at

time and %or each release. !ased on this in%ormation

lale SAPS, so%t6are release, CPU utilization, ne6

, you can easily calculate 6hether the hard6are 6ill e

cient y using a rule o% three.

ta Sizing o% a Production System

ao(e customer Hsee "re(ious o:, -esizing a Pro>

tion System has created a sizing %or a ne6 a""li>

on. According to the sizing, the a""lication 6ill

uire 1,'88 SAPS H')8 dataase SAPS and

on SAPS. hat needs to e done no6 is easyE &he

PS (alues must e added u", and the target utiliza>

must e determined.

&he e:isting hard6are is e(aluated as %ollo6sE

#ataase ser(erE ),888 SAPSO the t6o a""lica>

onsE ',388 SAPS each

&he current net SAPS consum"tion %or the data>ase is 1,28 SAPS Hi.e., ) o% ),888 SAPS and

,088 SAPS at the a""lication le(el Hi.e., 22 o%

,288 SAPS

the dataase, this 6ould mean the %ollo6ingE 1,28

S V ')8 SAPS X 1,288 SAPS ; 6hich re"resents a

ure utilization o% )8. &he a""lication ser(ers reach

28 SAPS and a utilization o% 3, 6hich could lead the

tomer to the conclusion that it 6ould ma+e sense to

another a""lication ser(er.

% you ha(e %ollo6ed the ao(e descri"tions o% tools

methods closely, you 6ill ha(e noticed that SAP

culates the standard sizings 6ith a target utiliza>

n o% 2/ and you should there%ore only use net

ounts. 7o6e(er, you should also ta+e into account

t the delta is ased on standard assum"tions as

l, and the 2/ %actor could e a use%ul uDer.

!ut i% you 6ant to ase your calculations on net

ounts, you can do so as %ollo6sE

&he net requirement o% the ne6 a""lication is 038

APS H1,'88 SAPS W 8.2/ target utilization. 128 SAPS

ut o% the 038 SAPS are allocated to theataase, 2'8 SAPS to the a""lication le(el.

Consequently, this means that 6e can e:"ect a

ro6th o% a""ro:imately 18 %or the dataase

nd a""ro:imately '8 on the a""lication side.


19/25

'.) Summary

U"grade Sizing

In u"grade "roects, customers usually im"lement

numer>

ous changes, 6hich include the SAP so%t6are,

dataase,

o"erating system, and an e:change o% hard6are. It

o%ten

ha""ens that the con$ guration and "arameter

settings are

changed as 6ell. All this can ha(e an im"act on the

num>

er o% 6or+ "rocesses, uDer settings, or other

things.1

U"grade sizing re%ers to the additional

requirements

o% SAP so%t6are. SAP uses regression tests to chec+the

resource consum"tion o% the most im"ortant

transactions

and to create a delta. &his in%ormation is made

a(ailale

to all customers in SAP 5otes, such as SAP 5ote

action * consumes an additional 8. &he CPU

and dataase consum"tions remain unchanged.

I% you ; as the customer ; no6 use &ransaction *

e:tensi(ely, this could cause "rolems 6hen calcula

ing the main memory. &he est thing to do is to calcu

late a est case and a 6orst case.

Memory H!est Case

'2*! Hout o% 'E '2*! W 1.8/ YX '0.*!

Memory Horst Case

'2*! W 8 X .3*!

Proaly, the %uture memory requirement 6ill

6ithin that range.

1 Since this is a (ery com"le: suect, SAP "ro(ides the SA*oingi(e 4unctional U"grade Chec+ ser(ice as "art o% thstandard ser(ice co(erage Hsee also Section 0.', Feri$ catio(ia Su""ort Ser(ices. &he SAP *oingi(e 4unctional U"gradChec+ includes a sizing "rocess.


20/25

e>Instance Proects

m the "oint o% (ie6 o% sizing, the maority

ngle>

nce "roects in 6hich com"anies change

a est>

eed strategy'to a single>instance strategy

so%t>

(endor, all data in one system

esent a mi:ture o% resizing and delta

g, sometimes also u"grade siz>

5ote that an u"grade sizing must e

ormed $ rst to ma+e sure that identical

itions a""ly.

nsiderations in the Conte:t o% a

gle>Instance Study

ustomer uses se(eral SAP and legacy

tems ino"e. &his customer no6 6ants to

solidate its

o"ean and American systems .

sequently, this

ans the %ollo6ingE

% the SAP so%t6are has diDerent release

ersions,

n u"grade sizing must e "er%ormed $

st. &he rel>

(ant %actors 6ill e u"graded so that all

ystems

a(e the same (ersion.

&he ne:t ste" in(ol(es resizing the SAP

o%t6are

ased on the same release (ersionO that

s, the cur>

ent consum"tions o% e:isting SAP

ystems must

e analyzed and totaled.

inally, a delta sizing must e "er%ormed

or the

egacy so%t6are. Ultimately, the

dditional require>

ments %or the ne6 so%t6are are added to

he e:ist>

ng load.

Summary

use SAP so%t6are sho6s a high degree o%

il>

ou can consider a linear change in

um"tion as

en %act. &he same a""lies to hard6areE I%

you 6ant

to e:tend the "rocessing "o6er o% a""lication

ser(ers,

you can add more ser(ers, re"lace the CPU , or add

more

CPUs, de"ending on your s"eci$ c "roduction model.

7o6e(er, a ne6 a""lication ser(er aDects the

data>

ases memory requirements ecause it in(ol(es

theaddition o% ne6 dataase users. A higher (olume

gener>

ally means an increase in read and 6rite acti(ities,

6hich,

in turn, may ha(e an im"act on the dis+ susystem.

' In a est>o%>reed strategy, you al6ays choose the"rod>

uct %rom the est (endor %or each Htechnological area.&he

diDerent "roducts are then connected 6ith each other(ia

inter%aces.

666.sa">"ress.com1/


21/25

' Sizing Methods

&he sizing method used essentially de"ends on theinitial

"osition youre in. !asically, there are diDerent

methods %or an initial sizing, 6hich can e

ma""ed (ia standard tools, and %or a "roduction

sizing, 6hich uses "roduction data as a asis %or

%orecasting.

In this cha"ter, 6e ha(e mentioned se(eral

times that

although sizing tools are (ery use%ul, they are

suect to



22/25

ain limitations. &hese limitations "rimarily de"end on

6ay in 6hich usiness "rocesses and the associated

cation so%t6are interact 6ith each other. 4or this

on, the %ollo6ing cha"ter, Sizing A""roaches HCha">

, descries ho6 you can con(ert user>ased and

ugh"ut>ased sizings into algorithms, and discusses the

and cons o% diDerent sizing a""roaches.


23/25

Inde:

'>tier im"lementation )0

>tier im"lementation )0

38='8 rule /

AA=P HA(erage and Pea+ ))

Acti(e user '1

Ad(anced sizing 18

Analysis

o% customer data 11

o% customer "rocesses 11

"er%ormance monitor /1

transaction design 28

A""lication monitor HS&80

/) A""lication "ro$le 01

A""lication ser(er 1), 1ased

a""lication '/, )0

Ja(a Firtual Machine HJFM /0

666.sa">"ress.com 180


24/25

Inde:

ey "er%ormance indicator 1', 10, 1

andsca"ing 2, 0', 03

atency 1on user '1

ogical #e"loyment Unit H#PU )2

M

Master data sizing '', '2

Ma:imum 9:tended Memory in

&ransac>

tion /0

Memory consum"tion 1

Memory requirement )8, /', /2,

/0 Methods 0

Minimum requirement /

55amed user '8

5et6or+ load 1user analysis 1'

Single record statistics HS&A# /2

Sizing

a""roach 10

y through"ut ''

y users ), '8

de$nition e:"ressi(eness 0

%ormula '

in%ormational (alue 1

initial 3

methods 0, 3, 11, 12,

'0 measurement 1'

oect )/

"rinci"le

"roduction 3, /1, 2

"roduction sizing 1

result )8, )2

sco"e '8through"ut>ased 3,

)) tool 11, 'ased '8, 3

(eri$cation /ased CPU sizing

)/ &hrough"ut sizing '', '

&hrough"ut sizing model '

&hrough"ut (olume 0

&otal cost o% o6nershi" H&C?

) &race tool /1, /0

&ransaction #!8' /


25/25

Inde:

&ransaction S&8/ /0

&ransaction S&82 /'

&ransaction S&80 /)

&ransaction S&A# /2

UU"grade "hase 3

U"grade sizing 1, 1/, 2, 20,

0/ Usage ty"e )0

User

acti(e '1

concurrent '1

interaction ste" /', /0

logged>on '1

named '8

User>ased sizing '8, 3User interaction ste" /0

FFeri$cation 00

o% sizings /

sap sizing

Documents