qs best pract v42

8/19/2019 QS Best Pract V42

http://slidepdf.com/reader/full/qs-best-pract-v42 1/26

Quick Sizer – Best Practices

Document Version: 1.0 – 2016-02-23

CUSTOMER

Quick Sizer Best Practices, Versions 42/ 242




Disclaimer

CUSTOMER

© 2016 SAP SE. All rights reserved. 2

Disclaimer

Some components of this product are based on Java™. Any code change in these components may cause

unpredictable and severe malfunctions and is therefore expressly prohibited, as is any decompilation of these

components.

Documentation in the SAP Service Marketplace

You can find this documentation at the following address:http:/ / service.sap.com/ sizing.

http://service.sap.com/sizing





Typographic Conventions

CUSTOMER


Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, table names, and key concepts of a programming language when theyare surrounded by body text, for example, SELECT and INCLUDE.

Exampl e Output on the screen. This includes file and directory names and their paths, messages,

names of variables and parameters, source text, and names of installation, upgrade and

database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they

appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters

with appropriate entries to make entries in the system.

EXAMPL E Keys on the keyboard, for example, F 2 or ENTER.




Document History

CUSTOMER


Document History

QS Version Date Change

30 2012-12-04 Usage of new template

Update of recommendation for very large projects

31 2013-03-05 New Quick Sizer version

32 2013-06-11 Chapter 3.3.1 Result Tabs for 'Result', 'Combined Approach', and 'Classic

Approach' was updated (introducing result approach)

32 2013-07-15 Add recommendation for SAP Suite on HANA sizing to chapter 2.2

33 2013-09-03 Chapter 2.2 Limited Scope / Not in Scope was updated




37/ 237 2014-09-04 Introduction of Quick Sizer HANA version

37/ 237 2014-09-11 Update of chapter 3.3.1 regarding example projects for Quick Sizer HANA

version

38/ 238 2014-12-03 Buttons Short/ Long Text changed to More/ Less Details, user-based sizing

with mandatory input field for residence time, if disk is calculated

38/238 2015-03-10 Only corrections such as 'Tree of elements' changed to 'Input Navigation Tee'

39/239 2015-06-02 Wording corrections







Table of Contents

CUSTOMER


Table of Contents

1 Introduction.............................................................................................................................................. 6

2 General .....................................................................................................................................................7

2.1 Characteristics and Scope of Quick Sizer ............................................................................................................. 7

2.2 Limited Scope / Not in Scope ...............................................................................................................................10

2.3 Technical Settings .................................................................................................................................................12

3 Individual Quick Sizer Pages .................................................................................................................13

3.1 Entry Screen ...........................................................................................................................................................133.2 Details on Quick Sizer Questionnaires .................................................................................................................13

3.3 Quick Sizer Result Page ........................................................................................................................................17

3.3.1 Result Tabs for 'Result', 'Combined Approach', and 'Classic Approach' .........................................18

3.3.2 Some Rules for SAPS ............................................................................................................................18

3.3.3 Result-Specific Sizing Elements ..........................................................................................................19

3.3.4 Note for Good Response Times.................................................................................................... 19

4 Definitions ..............................................................................................................................................21

5 Feedback.................................................................................................................................................22

6 Appendix ................................................................................................................................................. 23

6.1 Quick Sizer Classisc Version and Unicode .........................................................................................................23

6.2 Example of Workaround for the Sizing of Older SAP ERP Releases ................................................................24




Introduction

CUSTOMER


1 Introduction

Over the last couple of years we have received feedback and questions regarding Quick Sizer usage. As some of

these questions are recurring frequently, we have created this document to help more advanced users use the

tool. Please note that it is not a compendium of all Quick Sizer characteristics, but basically a collection of

answers to questions we have given in the past. It is more comprehensive than the existing FAQ for Quick Sizer.

We assume that you have already studied the document Quick Sizer for Beginners, which is located either on the

logon screen of Quick Sizer or at http:/ / service.sap.com/ sizing.

On the Service Marketplace you will also find a number of documents that describe the usage and the background

of sizing and sizing guidelines in more detail.

This document begins by describing some general characteristics of Quick Sizer, what is within the scope of the

tool and what isn’t. The next chapters deal with the usage of the tool and particularities of individual screens and

functions.

This document is a work-in-progress.



http://service.sap.com/~sapidb/011000358700000523272005E







General

CUSTOMER


2 General

In this section we describe general design guidelines of Quick Sizer.

2.1 Characteristics and Scope of Quick Sizer

Initial sizings only

You can only use Quick Sizer to size new (or initial) sizings of SAP standard solutions, meaning that you are either

planning a new installation of SAP software or you are planning a delta-sizing (you already have SAP software, for

example SAP CRM, and want to add new SAP software, for example SAP ERP).

Quick Sizer does not contain all SAP applications

When analyzing the resource consumption of a productive system, you quickly learn that roughly 80% of the

capacity requirements are occasioned by 20% of the transactions (80/ 20 rule). This means that not all

applications are included in Quick Sizer and never will be. Also, the sizing questions focus on the most

performance intensive business scenarios.

If you cannot find a particular application or partial solution in Quick Sizer, there may be different reasons for this,

such as:

· The application’s performance impact is negligible

· The application is very new and SAP prefers to do a one-on-one sizing with the help of spread sheets, for

example

· The application may be sized with a simple t-shirt sizing algorithm

· Quick Sizer does not size custom coding (also see below)

You find all available sizing guidelines athttp:/ / service.sap.com/ sizing.

Quick Sizer has two flavors: Quick Sizer classic version and Quick Sizer HANAversion

Here some details about this two versions of the Quick Sizer tool.

Access

You can access the versions via service.sap.com/quicksizer : Choose the appropriate tool: Classic version or

HANA version.






General

CUSTOMER


Projects

Quick Sizer projects will only be displayed and can only be accessed in the Quick Sizer version in which they were

created. That means, if you create a project in the classic version, you can access this project only using the

classic version and if you create a project in the HANA version, you can access this project only using the HANA

version.

As all Quick Sizer projects use the same name space, projects cannot have the same name in the classic and

HANA version of the Quick Sizer tool.

Questionnaires

You will find

· some of the sizing questionnaires in both Quick Sizer versions (e.g. ERP Sales),

· some only in the classic version (e.g. SAP NetWeaver Business Warehouse), and

· some only in the HANA version (e.g. HANA sizings).

Input

There are no different input fields for the classic and HANA version of the Quick Sizer tool.

Calculation checks

There are differences regarding calculation checks for the classic and HANA version of the Quick Sizer tool. For

example, in the HANA version for 'DB memory' and 'total memory' there is no more check that average is lower

than peak sizing.

Calculation details for Quick Sizer HANA version

Aggregation logic of DB memory does not correspond with classic DB memory, but with LiveCache. This meansthat there is no differentiated chronologically process, occuring values will be added also if they occur in different

time slots.

DB memory = classic DB disk * X

DB disk = DB memory * Y

DB SAPS = classic DB SAPS * Z

With X, Y, and Z as constants.

DB memory is only calculated when disk space is calculated. At last that means that for almost all peak sizings

and some user-based sizings there will be no DB memory calculated.

Output

For Quick Sizer HANA version there is an additional category for memory displayed.

Current releases only

Quick Sizer sizes the current releases of the solution. Do not use Quick Sizer for post golive sizings, such as

upgrade sizing (also see below).




General

CUSTOMER


Online questionnaire

Quick Sizer calculation is only available online to avoid versioning issues. There are offline versions of Quick Sizer

(EXCEL documents) available for Technology Partners at http:/ / service.sap.com/sizing and upon request, weoffer two offline versions of the Quick Sizer (classic and HANA). This questionnaires can be used to collect sizing

relevant data within the company. Please note that this Excels cannot be used to calculate results, these are a

data collection vehicle only. You must then copy and paste the collected data into the corresponding Quick Sizer

version classic or HANA to get sizing results. For every new Quick Sizer version, there will be two corresponding

offline data collection questionnaires available.

Availability

Quick Sizer is available 24*7, with the possible exception of quarterly updates where the tool may be down for two

days on a weekend.

Quick Sizer results

Quick Sizer results contain requirements for CPU, memory, disk, and disk I/ O. In the case of CPU, SAP offers

hardware-independent figures such as SAPS (for more information on SAPS see

http:/ / www.sap.com/benchmark). For corresponding hardware configurations contact your hardware partners.

Quick Sizer documentation

There is a variety of information available about Quick Sizer: On the entry screen there is a link to a presentation

Quick Sizer for Beginners in which all functions of Quick Sizer are explained.

In Quick Sizer there are several links to more information:

· Quick Sizer tool documentation links to a documentation where you find a description of how Quick Sizer can

be used.

· How t o fill in the questionnaire links to explanations of the corresponding questionnaire.

· Also, you get information on mouse-over, for example for the sizing elements.

For additional information on Quick Sizer see http:/ / service.sap.com/sizing.

Quick Sizer projects created before July 2005

The projects of the 'old' Quick Sizer are available for display only, because the 'old' Quick Sizer has been replaced

by the 'new' Quick Sizer. Unfortunately, migration of project data is not possible.

Quick Sizer and Unicode

Please note that Quick Sizer results include Unicode requirements since version 6 (December 2006). As of

1.1.2009, all SAP benchmarks are Unicode benchmarks. But if you want to compare Quick Sizer Unicode result

with a non-Unicode benchmark result, you may use this workaround: deduce 10% processing capabilities from


http://www.sap.com/benchmark


http://www.service.sap.com/~sapidb/011000358700000523272005E














General

CUSTOMER


the configuration. For example: a configuration that ran a non-Unicode benchmark and was rated 8000 SAPS, is

likely to achieve 7200 Unicode-SAPS. For more information refer to the Unicode pages on the Service

Marketplace at http:/ / service.sap.com/ unicode.

Find more detailed information about Quick Sizer and Unicode in the appendix chapter 6.1.

2.2 Limited Scope / Not in Scope

For easier analysis, there are Very large projects

For easier analysis, there are also result categories, ranging from extra small (XS) to extra large (XXL). The

categories are to provide some estimate what size your project is in relation. XXL may not indicate a very large or

even too large sizing. It means that you should not only rely on the current Quick Sizer results alone, but that you

should verify the consistency of your inputs and evaluate whether an expert sizing is needed.

If you did both sizing methods and the category exceeds XXL, you should also contact the hardware vendor or

SAP for further assistance, because in the complex world of business applications tools only have a limited scope

of validity. For large projects the possible difference between the estimation and the real resource consumption

might be in a range that costs a significant amount of money.

Upgrade, re-sizing

Not in scope are post go-live sizings (except delta sizing of new SAP solutions). Therefore, a report that gets real

data from a live system and loads it into Quick Sizer does not make any sense.

Note that there are two types of upgrade: technical and funct ional.

A technical upgrade is an upgrade from one release to the next higher release of a particular SAP solution

(e.g. SAP R/ 3 Enterpriseà SAP ECC 6.0). In this case, significant differences with regard to architecture

and functionalities are not expected (performance will not change significantly).

A technical upgrade is an upgrade from one release to the next higher release of a particular SAP solution

(e.g. SAP R/ 3 Enterpriseà SAP ECC 6.0). In this case, significant differences with regard to architecture

and functionalities are not expected (performance will not change significantly).

Since sizings using Quick Sizer are based on specific scenarios and contain many assumptions, QuickSizer is not the appropriate tool to size technical upgrades. It is much more accurate to measure the

current resource requirements of the system and adding the requirements of the new release. SAP

provides upgrade notes with information about additional resources for CPU, memory, and disk when

upgrading from one release to another.

Functional upgrades are upgrades with significant changes in functionality and/or architecture (e.g. SAP

CRM 2007à SAP CRM 7.0). In this case, you can use the following sizing approach using Quick Sizer:

1. Analyze your system to measure the current resource requirements

2. Create a Quick Sizer project based on the current (old) release (e.g. SAP CRM 2007)

3. Create a Quick Sizer project based on the new release (e.g. SAP CRM 7.0)

4. Define the upgrade factor (result quotient between both Quick Sizer projects)

http://service.sap.com/unicode






General

CUSTOMER


5. Extrapolate the resource requirements of your current system by this factor

Workaround for the sizing of older SAP ERP releases

If you need to size an older SAP ERP release than the one in Quick Sizer, you can use Quick Sizer anyhow and

make a retro-calculation with the help of SAP Notes (778774, 107056 Quick Sizer for 4.6 C systems, etc.; inverse

upgrade sizing, example see appendix)

Upgrade Sizing within Major Releases

If you need to size an older SAP application release than the one in Quick Sizer, you can use the Quick Sizer

anyhow, when the major release is the same. For example, you want to size SAP NetWeaver Process Integration

7.0 and the Quick Sizer SAP NetWeaver Process Integration release is 7.3, you can use the Quick Sizer. The

possible error coming from the different releases is smaller than the errors coming from the inaccuracies in the

inputs and the algorithm.

Configuration or landscaping

Configuration or landscaping are not in scope of Quick Sizer; for example, Quick Sizer does not give any

recommendations on which software to install on which server.

Customer coding

Quick Sizer is for initial sizing only. Customer developments cannot be included in the Quick Sizer tool (see also

scope). Customer programs have to be measured to check the runtime behavior with appropriate performance

tools (e.g. transaction STAD). The possibility exists for customers to create their own sizing guideline (Check the

documentationSizing and Hardware Capacity Planning (TechEd 2011) on the SAP Service Marketplace

service.sap.com/ sizing)

Sizing platform-type SAP software

SAP NetWeaver capabilities such as SAP NetWeaver Business Warehouse (BW), SAP NetWeaver BW powered by

SAP HANA, or SAP NetWeaver Portal have questionnaires within Quick Sizer, but have to be handled carefully: For

example, it is very difficult to foresee which highly complex selects will be generated in SAP NetWeaver BW and

how their performance will be. This is an example of report-natured transactions, but for the most highly generic

SAP tools there are no sizing estimations. They have to be measured (e.g. with transaction STAD). Also, generic

functionality, meaning applications with a large degree of automation, such as variant configuration, is not in

scope of Quick Sizer.

http://www.dict.cc/englisch-deutsch/inaccuracies.html




http://www.dict.cc/englisch-deutsch/inaccuracies.html




General

CUSTOMER


2.3 Technical Sett ings

Quick Sizer Settings

Printer configuration for optimal printing within Quick Sizer: For the most optimal printout choose the following

settings in your browser, e.g. MS Internet Explorer:

· View→ Text Size → Medium

· File→ Page Setup→ Orientation → Landscape → Paper→ A4

Browsers supporting Quick Sizer

Please refer to SAP Note 598860 Browser supported by BSP to get information about which browsers supportQuick Sizer (Desgin2003).

http://service.sap.com/sap/support/notes/598860




Individual Quick Sizer Pages

CUSTOMER


3 Individual Quick Sizer Pages

3.1 Ent ry Screen

Searching for your own projects

In principle, Quick Sizer allows everyone to access any project. The only input that is required is the customer

number and the project name. Quick Sizer search capability, however, is limited to projects that you have already

accessed before.

For security reasons you cannot search for all projects or for all projects with a specific customer number.

3.2 Details on Quick Sizer Questionnaires

Project information questionnaire

This questionnaire is for information purposes only. There is no influence on calculation and the inputs are not

considered in the result.Exception is the choice whether it is a new system or a system extension:

Per default, for New SAP Business Solution/ Software Component (with minimal offsets) the gross results are

displayed on the result page for solution level. If you chooseSAP Business Solution/ Software Component

Extension , net results are displayed. These offsets may be different for each solution (Note: your choice (New SAP

Business Solution/ Software Component orSAP Business Solution/ Software Component Extension ) on the project

information questionnaire will be saved for the whole project. Your choice on the result page won’t be saved).

User-based Sizing

If an user-based sizing calculates disk, you have to fill-in the residence time in months.

Input number format

Quick Sizer does not accept input of numbers with decimal places; only natural numbers (except for in the short

text and comment field).





CUSTOMER


Influence of workdays on average sizing

The number of workdays has an impact on the following sizing results:

· User sizing: disk size (number of users multiplied by workdays per year)

· Throughput sizing: average CPU and disk I/ O (number of objects per year divided by the number of workdays

and their duration)

Therefore, whenever you change the number of workdays, the results for the above mentioned categories change

as well.

Average and peak sizing: two separate calculations

If you use throughput sizing you have to fill in data for average and/ or peak sizing (field A/ P : Average or peak

load). In average sizing, objects for a whole year have to be considered; in peak sizing you have to define howmany objects will be processed in which time frame per day (referred to as period).

There is a dependency between the fields A/ P and TI (Time Interval): Normally, as mentioned before, for average

this is a year and for peak these are hours, because customers are most familiar with these units.

In Quick Sizer the result for a peak sizing of a sizing element has to be higher than the result of an average sizing of

the same sizing element at the same time (meaning hour of the day). Otherwise, Quick Sizer shows an error

message. There may be situations, however, in which it is necessary to add peak sizing to average sizing. In these

cases you can make use of the ID (identity) field.

Example (based on Quick Sizer classic version)For average age sizing you entered 1,000,000

objects with 10 items, 12 months residence time, 9 am - 6 pm of two sizing elements SD-SLS for two

different subsidiaries and 100 objects with 10 items from 12pm - 13pm, and 10,000 objects with 10 items

from 12pm - 13pm for peak sizing of two sizing elements SD-SLS for two different subsidiaries,

you get 1034 SAPS as overall result on result level Sizing element s + choice (only the peak result is shown

as the overall result). This seems to be ok, but does not reflect the connection between average and peak

sizing of each subsidiary.

To do this, fill the ID field: For example enter '1' into the ID-field of the average and peak sizing element

SD-SLS for the Spanish subsidiary:





CUSTOMER


Now an error message is shown, which explains that the peak result for the entry of the Spanish

subsidiary has to be higher than the average result for the entry of the Spanish subsidiary and you have to

rethink these inputs, because they do not match.

So the ID-field can help you to reflect your business more correctly in Quick Sizer.

Project statuses

There are the following project statuses within Quick Sizer:

· Without entries : project with no input yet (owner: customer).

· In progress : customer enters data into a project and saves it (owner: customer).

· GoingLive: (for a project which was set to this status by the customer)

o Now there are two different projects with two different owners for one project name.

o Project of owner customer is ‘read only’.

o Customer can switch in display mode between her/ his project and the project owned and changed by

GoingLive.

o GoingLive can switch between display mode of the project owned by the customer and change mode of

the GoingLive project. GL can set the status ("In progress…").

· In progress after GL:

o This status is set by the GoingLive team after the GoingLive check.

o Project of owner Going Live is ‘read only’, project of owner customer can be changed.

· Final : Set this status when a project should not be changed anymore, copy with reference is still possible

· Inactive : Projects will not be displayed when you search for your projects, they also cannot be copied or

changed anymore. This is a kind of deletion.





CUSTOMER


Columns % chg. / % dsp. in Quick Sizer throughput tables

This means the number of changes and displays to an object in percent. A display or change is almost equally

expensive as creating a business object.

If you enter 100, every object is changed or displayed. If you enter 50, every other object is changed or displayed.

If you enter 300, every object is changed or displayed three times.

Example (based on Quick Sizer classic version)

When you fill in 10,000 objects with 10 items for peak sizing of SD-SLS (12pm – 13pm),

you get approximately 1000+ SAPS as overall result on result levelKey capabilities .

When you enter 100 in the % chg. field (this means: one change),





CUSTOMER


The overall result on result levelKey capabilities has nearly doubled: 2000+ SAPS

3.3 Quick Sizer Result Page

Quick Sizer CPU result at 65% CPU utilization

The CPU sizing results are calculated against an average target CPU utilization of 65% for throughput-based

sizings (and 33.3% for user-based sizings) to achieve predictable server behavior. Ideally, You would observe

65% CPU utilization if you ran the same processes used in Quick Sizer and purchased hardware to meet the CPU

sizing recommendations, which are measured according to the SAP Application Performance Standard (SAPS).

As the Quick Sizer tools calculates for 65% utilization, you can use this value to check with existing benchmarks

results. You do not have to do any more calculations.

Note: For good response times choose CPUs with a good single-thread performance. See also chapter 3.3.4 Note

for good response times.





CUSTOMER


3.3.1 Result Tabs for 'Result ', 'Combined Approach', and 'ClassicApproach'

Check online documentation on and following example projects based on Quick Sizer classic version

· __Resu lt s_1 V22 F with customer number 188213



and following example projects based on Quick Sizer HANA version

· __Resu lt s_1 / HANA with customer number 188213



for SAPS example calculations for the result, combined, and classic approach.

3.3.2 Some Rules for SAPS

SAPS distribution application server to database server

This distribution is provided on a number of result levels (such as software component, for example).

Total SAPS seems lower than the sum of individual SAPS

The reason for this is the following: Quick Sizer calculates individual peaks for each component during 24 hours,

including the SAPS total value. The example based on Quick Sizer classic version below shows Quick Sizer results

for 3 hours.

Table 1: Example for SAPS calculation per hour

PP S PS DB S PS S PS Total

Hour 1 100 1000 1100

Hour 2 1000 100 1100

Hour 3 600 600 1200

→ DB-SAPS = 1000, APP-SAPS = 1000, SAPS TOTAL = 1200

This means, if you run the application and the database on different servers, you need 1000 SAPS on each. If you

run them together you need 1200 SAPS.

http://service.sap.com/~sapidb/011000358700000479942013E/level1.htm

http://service.sap.com/~sapidb/011000358700000479942013E/level1.htm





CUSTOMER


Although, theoretically, it applies that SAPS total <= DB-SAPS + APP-SAPS, in reality they are added when both

peaks occur in the same time interval, which is more or less true in most cases, because the relation between

APP-SAPS and DB-SAPS is quite similar in most applications.

3.3.3 Result-Specific Sizing Elements

Sizing elements ADD-DISK/ ADD-UPL-M in the BW sections for Quick SizerClassic Version

These sizing elements are only used for calculation purposes. You will not find them on the BW entry screen. ADD-

Disk refers to additional disk space for the UPLOAD on the database.

ADD-UPL-M refers to additional memory demand for the UPLOAD. Both figures depend on the size of the largest

infocube/ DS object and are calculated at runtime.

3.3.4 Note for Good Response Times

There are two different widely independent performance KPIs for systems - throughput and server response time

for single processes. Systems are designed and optimized for highest throughput or fastest response times or

lowest power consumption or other features such as RAS (redundancy, availability, serviceability). The

combination of characteristics with every hardware is unique.

In order to increase the awareness we introduced the new KPI Single Computing Unit performance (SCU

performance). To be as hardware neutral as possible and due to virtualization technologies we use the term Single

Computing Unit performance instead of single thread performance.

There are some SAP applications that benefit from a good Single Computing Unit performance. This is especially

valid for SAP CRM, SAP SRM and some business processes in SAP EWM.

When sizing one of these SAP applications, customers should discuss this topic with their hardware partners.

Hardware partners should make sure that the Single Computing Unit performance of the planned system is

sufficient to fulfill the response time expectations of their customers.

With the introduction of the Single Computing Unit performance classes, every sizing element is classified. The

classes are A, AA, and AAA.

Table 2: Overview about Quick Sizer single computing unit performance classes

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.

The classes are aggregated along the different result levels (from sizing element to project) and within same time

slots.





CUSTOMER


Table 3: Aggregation of results to next result level and aggregation within same time slots

A A AA AAA

AA AA AA AAA

AAA AAA AAA AAA

Example (based on Quick Sizer classic version)

· SAP ERP SCU performance A for 10am to 12 am and SAP CRM SCU performance AAA for 11am to 1pm

· Aggregation to result levelProject shows:

o For time slots: SCU performance A from 10am to 11am and AAA from 11am - 1pm

o Total result: AAA (for 24 hours)

For more information checkSAP note 1501701.

http://www.service.sap.com/sap/support/notes/1501701

http://www.service.sap.com/sap/support/notes/1501701




Definitions

CUSTOMER


4 Definitions

SAP user definitions

· Named users are licensed users (transaction SU01)

· Logged-on users: By definition they processed a logon procedure and are able to work with the system.

Depending on the architecture of the system they consume different resources in the system (transactions

AL08, ST07, SM04)

· Concurrent users work simultaneously or concurrently in the system. They consume system resources at the

same time, e.g. memory or CPU (transaction SM51, SM50)

· Active users are like concurrent users, only with a time stamp (within the last ten minutes, transaction ST07)




Feedback

CUSTOMER


5 Feedback

Feedback is very welcome; please send it to Dagmar Kirsamer ([email protected]), Product

Management Performance, Architecture, Scalability.

mailto:[email protected]




Appendix

CUSTOMER


6 Appendix

6.1 Quick Sizer Classisc Version and Unicode

Since Quick Sizer was switched to Unicode Sizing (from version 6, December 12, 2006 onwards), the following

applies:

1. CPU: The SAPS calculation was not changed for Unicode. Customers or hardware partners have to take

“Unicode-SAPS” as a basis for the hardware configuration, i.e. for the SAPS value of a machine a Unicodebenchmark must be available. In case of non-Unicode benchmarks, partners need to convert the values

as appropriate.

2. Memory: The calculated memory requirements were adapted to Unicode requirements as follows: In the

case of additional memory requirements through Unicode, 50% of the existing requirements was added.

3. Disk: Disk sizing is Unicode-dependent, but is not considered in Quick Sizer for the following reasons:

A. The impact of Unicode strongly depends on the database used (whereas the calculations in the Quick

Sizer are database-independent). Example:

• Unicode encoding of the database (UTF-8, UTF-16, UCS-2)

B. Due to compression of fields on the database level, the influence on disk space is smaller than the

influence on memory.C. The Unicode effects strongly depend on the application and its usage by the customers.

• Portion of character fields

• Utilization level of the character fields

• Compression of character fields

D. In Quick Sizer, disk sizing is calculated by determining the number of rows in the tables of business

objects (mainly transaction data). For each of these tables, the number of entries is multiplied with the

width of the table structure in the database. The disk requirements for all indexes of the tables are

added in the same way.

In addition to Unicode, the following potentially significant influencing factors are also not taken intoconsideration. This is because their effects are highly dependent on database, application, and customers

requirements (similar to Unicode):

· Utilization level of database blocks (is not always 100%)

· Technical administration tables (e.g. spool tables)

· Application and administration data (customizing, master data)

· Non-active indexes

· Customized indexes

· B-tree structure (depends on the number of entries in the table and on the selectivity of the index in each

specific case)




Appendix

CUSTOMER


These factors have such a complex influence on the calculated disk space that it is not included into the

calculation. The influencing factors are dependent on the database and the application and are customer-specific.

In addition, the variety of influencing factors leads to complex logical interdependencies that affect disk

requirements. For example, when implementing Unicode, the required disk space has been seen to decline: While

the net disk space increases when using Unicode (depending on the database coding), the reorganization of the

database tables, as a result of using Unicode, increases the utilization level of the database blocks resulting in a

reduction of the gross disk space needed.

6.2 Example of Workaround for the Sizing of Older SAP ERP

Releases

Example of retro-calculation SAP ERP 6.0 to SAP R/ 3 4.6C:

· Note 517085 shows CPU (+ 0 - 5%), memory (+25%), and disk1 (+ 0 - 5%) for SAP R/ 3 4.7x110 taking as

base SAP R/ 3 release 4.6C, SR2

· Note 752532 shows CPU (+ 5 - 10%), memory (+ 5 - 10%), and disk2 (+ 0 - 5%) for SAP R/ 3 4.7x200 taking

as base SAP R/ 3 release 4.7, EE1.1

· Note 778774 shows CPU (+ 5 - 10%), memory (+ 5 - 10%), and disk3 (+ 0 - 5%) for SAP ECC 5.0 taking as

base SAP R/ 3 release 4.7, EE 2.0

· Note 901070 shows CPU (+ 0 - 5%), memory (+ 5 - 10%), and disk4 (+ 0 - 5%) for SAP ECC 6.0 taking as

base SAP ECC 5.0Adding up all of these delta estimations, the estimated hardware resources for SAP R/ 3 4.6C to SAP ERP 6.0

would be:

· CPU:

Low: 1.0 * 1.05 *1.05 * 1.0 = 1.1025à 10.25%

High: 1.05 * 1.1 * 1.1 * 1.05 = 1.334à 33.4%

Avg: 1.025 * 1.075 * 1.075 * 1.025 = 1.214 à 21.4%

· Memory:

Low: 1.25 * 1.05 * 1.05 * 1.05 = 1.447à 44.7%

High: 1.25 * 1.1 * 1.1 * 1.1 = 1.6637à 66.37%

Average: 1.25 * 1.075 * 1.075 * 1.075 = 1.5528 à 55.28%

· Disk:

Low: 1.0 * 1.0 * 1.0 * 1.0 = 1.0 à 0 %

High: 1.05 * 1.05 * 1.05 * 1.05 = 1.215 à 21,5 %

Average: 1.025 * 1.025 * 1.025 * 1.025 = 1.1038à 10,38 %

1 Disk strongly depends on the database and the implemented business scenario.







Appendix

CUSTOMER


So, for this case, Quick Sizer V16, which is based on SAP ERP 6.0, can be used to size an older SAP system. You

would need to figure reductions of 21% of CPU, 55% of memory, and 10% of disk to get the results for SAP R/ 3

4.6C.



www.sap.com/ contactsap

© 2016 SAP SE. 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 SE.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP SE 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 ads, 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 is a registered trademark of Oracle Corporation.

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.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

J ava is a registered trademark of Sun Microsystems, Inc.

J avaScript is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

SAP, R/ 3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP Business ByDesign, and other SAP products and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP SE in Germany and in

several other countries all over the world. 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.

These materials are subject to change without notice. These

materials are provided by SAP SE and its affiliated companies ("SAP

Group") for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or

omissions with respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in the

qs best pract v42

Documents