architecture difference between nw 7.0 and 7.1

Using the QuickSizer Version 23 –Rough Guide

Released for SAP Customers and Partners

March 2011

Sizing Guide

Released for SAP Customers and Partners

© Copyright 2011 SAP AG. All rights reserved.

No part of this publication may be reproduced ortransmitted in any form or for any purpose without theexpress permission of SAP AG. The informationcontained herein may be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components ofother software vendors.

Microsoft, Windows, Outlook, and PowerPoint areregistered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, ParallelSysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,Intelligent Miner, WebSphere, Netfinity, Tivoli, andInformix are trademarks or registered trademarks of IBMCorporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registeredtrademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame,WinFrame, VideoFrame, and MultiWin are trademarks orregistered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of SunMicrosystems, Inc., used under license for technologyinvented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAPNetWeaver, and other SAP products and servicesmentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG inGermany and in several other countries all over theworld. All other product and service names mentionedare the trademarks of their respective companies. Datacontained in this document serves informational purposesonly. National product specifications may vary.

These materials are subject to change without notice.These materials are provided by SAP AG andits affiliated companies ("SAP Group") for informationalpurposes only, without representation or warranty of anykind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The onlywarranties for SAP Group products and services are thosethat are set forth in the express warranty statementsaccompanying such products and services, if any.Nothing herein should be construed as constituting anadditional warranty.

DisclaimerSome components of this product are based on Java™.Any code change in these components may causeunpredictable and severe malfunctions and is thereforeexpressively prohibited, as is any decompilation of thesecomponents.

SAP Library document classification: CUSTOMERS &PARTNERS

Documentation in the SAP Service MarketplaceYou can find this documentation at the following address:http://service.sap.com/sizing

http://service.sap.com/sizing

© SAP AG Using the Quick Sizer - SAP Customers and Partners 1

TABLE OF CONTENTS

1 INTRODUCTION ................................................................................................................................... 2

2 QUICK SIZER AND SIZING KPIS ....................................................................................................... 2

2.1 SIZING THE CPU ................................................................................................................................ 32.2 SIZING THE DISK ................................................................................................................................ 32.3 SIZING THE MEMORY ......................................................................................................................... 4

3 QUICK SIZER – USER GUIDE ............................................................................................................. 5

3.1 QUICK SIZER FOR BUDGET SIZING....................................................................................................... 53.1.1 Sizing by Users .......................................................................................................................... 53.1.2 Sizing by Throughput ................................................................................................................. 5

3.2 ADVANCED SIZING WITH THE QUICK SIZER ......................................................................................... 73.3 QUICK SIZER FOR EXPERT SIZING ....................................................................................................... 73.4 QUICK SIZER AND GOINGLIVE ............................................................................................................ 8

4 INTERPRETING QUICK SIZER RESULTS ........................................................................................ 9

4.1 DIFFERENT RESULT LEVELS ............................................................................................................... 94.1.1 Result by Solution ...................................................................................................................... 94.1.2 Result at Software Component Level ......................................................................................... 114.1.3 Results, Statistics and Inputs Overview ..................................................................................... 124.1.4 Other Result Levels .................................................................................................................. 12

4.2 CLASSIC APPROACH AND COMBINED APPROACH ............................................................................... 124.3 FREQUENTLY ASKED QUESTIONS ON QUICK SIZER RESULTS .............................................................. 144.4 ADDITIONAL FUNCTIONS AND OPTIONS ON THE RESULT SCREEN ....................................................... 16

5 OVERVIEW OF FUNCTIONS AND OPTIONS IN THE QUICK SIZER ......................................... 16

5.1 DOCUMENTATION AND HELP ............................................................................................................ 165.2 FUNCTIONS AND OPTIONS IN ALPHABETICAL ORDER ......................................................................... 16

6 SOME TIPS ON CHECKING THE QUALITY OF SIZING PROJECTS ......................................... 21

6.1 ANALYZING THE RESULTS ................................................................................................................ 216.2 ASSESSING THE INPUT ...................................................................................................................... 22

7 FEEDBACK .......................................................................................................................................... 22


1 IntroductionThe Quick Sizer is the online sizing tool of SAP. The tool helps prospects, customers and hardwarevendors to Speed up hardware planning phase by asking structured questions relating to usage of business

processes that might affect sizing Facilitate tendering procedure by including links to hardware vendors so that they can make an

offer based on the information provided in the tool Provide content for GoingLive check to analyze, if the hardware is sufficient to smoothly run SAP

software

This document describes how to use the Quick Sizer and how to interpret the result of the tool. Fordetailed information on specific business process sizing guidelines, such as how to size ActivityManagement within SAP Customer Relationship Management, see the Quick Sizer online help ‘Howto fill in the questionnaire’.

Keep in mind that the Quick Sizer is a tool for initial sizings only. Out of scope are post go-live sizingssuch as upgrade or re-sizing (except delta sizing of a new SAP solution), configuration, landscaping,and customer coding. For post go-live sizings, check the corresponding document on the SAP ServiceMarketplace:”Sizings after GoLive: Resizing, delta sizing, upgrade sizing “(www.service.sap.com/~sapidb/011000358700004430262006E).

For more information on the principles of sizing and the theoretical background of SAP’s sizinginitiative see the background sizing document at service.sap.com/sizing Sizing GuidelinesGeneral Sizing Procedures.

2 Quick Sizer and Sizing KPIsThe goal of sizing is to plan hardware expenditures required to run SAP software. Hardwarerequirements can be expressed in terms of processing power, projected disk growth, physical disk I/O,memory consumption and front end network requirements for WAN connections. When analyzing theresource consumption of a productive system, you quickly learn that roughly 20% of all transactionsaccount for 80% of the capacity requirements. SAP’s sizing guidelines take this ratio intoconsideration: the Quick Sizer and its related guidelines help you transform information about yourmost important business processes into high-level requirements for CPU, memory, disk, and front endnetwork load.

The Quick Sizer is an online application on the SAP Service Marketplace that consists of severalquestionnaires and provides two sizing methods, user sizing and throughput sizing. If informationabout your planned SAP implementation is limited, we suggest a user-based sizing. If you have moredetailed knowledge of the SAP Business Suite and how you plan to implement it, throughput sizing isthe recommended option. Since throughput sizing requires more detailed information, it yields moreaccurate estimates of the hardware resource requirements.

SAP has derived the sizing guidelines implemented by the Quick Sizer by measuring the hardwareresource consumption of realistic business processes. This is achieved with the help of SAP StandardApplication Benchmarks, in-house measurements at SAP, and actual customer system experience.

Sizing is done on the basis of sizing elements, i.e. business objects or transactional documents thatare the result of a business transaction in SAP software. For example, in the course of a standardSales & Distribution (SD) process as defined in the SAP SD Standard Application Benchmark, thefollowing business objects are created and thus can be sized in the Quick Sizer: customer order,delivery note, goods issue, and billing document. Each sizing element is associated with particularhardware “cost factors” such as CPU, memory or disk. Let’s look into these cost factors in a bit moredetail.

http://www.service.sap.com/~sapidb/011000358700004430262006E).


2.1 Sizing the CPU 1

Both the user sizing and throughput sizing calculate the CPU resource consumption.

In the user sizing, the Quick Sizer assumes a certain CPU load depending on the business processand the user activity. This is a rather broad approximation but it makes the sizing very easy.

The more detailed method is the throughput sizing. To determine the CPU requirements, the QuickSizer uses the number of sizing relevant objects, their size, and the time frame in which they are beingprocessed. The number of data changes and displays also influences this processing power.

To make the sizer’s life easier, the Quick Sizer makes a number of assumptions, for example, it doesnot distinguish between document processing in background or in dialog mode. Also, it calculates thesame CPU consumption for "creating with reference" and “creating without reference”. Possibleoptimizations for mass processing, for example, in invoicing or goods movement, are not taken intoconsideration. That way, the assumptions are more expensive in some cases, and less expensive inothers, in general levelling out.

The result of CPU sizing is divided into requirements for the application and the database layer and isspecified in SAPS (SAP Application Performance Standard), rather than GHz. SAPS is a hardwareindependent CPU performance unit devised to describe the throughput power of a server, as CPUmeasurements are highly configuration dependent. It refers to the CPU-driven SD StandardApplication Benchmark (see also www.sap.com/benchmark): 2,000 fully business-processed order lineitems per hour equate to 100 SAPS.

This is important to know because the number of SAPS a specific configuration can achieve maychange between releases. If, for example, the resource consumption of release B differs from that ofrelease A, the number of line items processed by the configuration will change, and the number ofSAPS will be different, too. For example, a configuration that delivered 10,000 SAPS in release A willdeliver 9500 SAPS in release B, if release B has a 5% higher resource consumption.

It is also important to note that the CPU sizing result is calculated to a target CPU utilization of 65% asa safety calculation. As a consequence: If the Quick Sizer yields 10,000 SAPS and you provide ahardware worth of 10,000 SAPS, ideally the actual CPU utilization should be 65%.

At www.sap.com/benchmark you can view sample configurations and the number of SAPS they haveachieved. Customers can use this information to get a ballpark estimate for the required hardwareexpenditures.

2.2 Sizing the DiskDisk size capacity has grown rapidly in the past years. Even disks of 1TB+ have becomecommonplace. However, costs for data management depend on the size (planned down times,backup and recovery, and so on). Also disk sub systems, such as the I/O system are immenselyexpensive. Therefore SAP defined two disk-related KPIs: Database disk space and I/O.

Let’s first talk about, what is disk? For us, disk includes space for administration (e.g., SWAP andDBMS) which is a constant value for a certain project with constant size, and a DDIC data value thatincreases over time. In our predictions we cannot include DBMS-specifics such as compressionalgorithms.

Now, we take a look at the disk size calculation: the disk size calculation in user sizing is analogous tothat of CPU consumption. This means that the Quick Sizer assumes a specific disk value per user andworkday. In throughput sizing, disk growth is determined by the number of business objects per year,their size and the length of time they will remain in the database before they are being archived.

The following data instances that potentially have a certain influence on the disk size are consideredexceptions and are therefore disregarded:

1 For good response times choose CPUs with a good single-thread performance, especially for SAP CRM andSAP SRM.

http://www.sap.com/benchmark):

http://www.sap.com/benchmark


System source data defined by the minimum system requirements Objects that reside in the system for a very short time only. Typically, this includes "intermediate"

or temporary data such as IDocs, workflows, SPOOL jobs, batch input jobs, job logs, data that isdeleted automatically, purchase requisitions, planned orders created by the Materials RequirementPlanning run, incompletion protocols and due lists created by an order.

In the disk sizing method the Quick Sizer ignores small tables, hardware dependent tablecompression, and custom tables and indexes.

Master data usually does not contribute greatly to the overall disk sizing. In general document typedata has a much more significant impact on the disk size. However, some applications have many andlarge sets of master data (as Utilities, Insurance, Telecommunications), in these sizings, master dataare included.

An important factor in ascertaining the necessary disk size is growth rate. The growth rate istechnology-independent, because databases use very different compression algorithms. SAP hasdecided to only look at the database disk space from an SAP perspective to remain independent in thesizings

For reasons of better disk growth analysis, the Quick Sizer provides information about data archivingpossibilities, such as projected disk growth after one year, after the residence period, and informationabout whether archiving objects are available.

Another factor to consider is that space development has advanced much more quickly than theprogress in disk access times. Therefore, disk input/output (I/O) may become a bottleneck.

2.3 Sizing the MemoryAlthough demand for physical memory has increased significantly as new processor architectureimproved addressing of memory, in general, physical memory prices have gone down in recent years.As a result, the use of memory computing has become very popular for new memory–driven softwareapplications such as Business Warehouse Accelerator for increased analytical capabilities, orliveCache for planning. Unfortunately, advances in memory capacity are not keeping up with advancesin processor technology.

At the moment, the price ratio for memory and CPU capacity is 50:50 or in smaller configurations morelike 60:40 (e.g. 4-processor servers). Since physical space for memory slots is limited on a motherboard, the ratio is often affected by the fact that for smaller configurations you may be forced to use afew powerful and expensive memory cards instead of many inexpensive smaller ones. There may bemore slots available in larger systems.

In most cases, the highest contributor to memory consumption is the memory required by online users.System settings concerning buffers and caches may also influence the memory requirements of theapplication server. To account for this, the Quick Sizer assumes one application server as a memoryoffset and adds the user specific memory requirements according to your entries. In Java applications,the memory required by Garbage Collection also plays an important role and therefore is included inthe Quick Sizer’s memory sizing. SAP’s liveCache, which is used for business planning purposes,basically only consists of memory.

In user-based sizing, memory requirements are determined by the net consumption of the onlineusers. All other memory requirements, for example those of the operating system, need to be addedwhen the final configuration or system landscape is planned.

In the Quick Sizer, for the most throughput-based sizings 8/3 GB memory is calculated for each 1000SAPS. But there are few throughput-based sizings where the factor is another or memory is calculatedin a totally different way.


3 Quick Sizer – User GuideSAP’s Sizing initiative follows a two-way strategy. Currently, the Quick Sizer allows for different kindsof sizings: From simple user sizing, where you can get a ballpark estimate for initial sizings, to anadvanced throughput sizing where you can size for business objects up to an expert throughput sizingwhere you can account for multiple peaks and averages.

3.1 Quick Sizer for Budget Sizing

3.1.1 Sizing by UsersAs mentioned before, initial sizing, when you have only a vague idea of the expected workload isdominated by a user sizing. Sizing for your concurrent active users is pretty straight-forward in theQuick Sizer. It only takes into consideration users that are logged on and consume system resources,for example in the Portal or in SAP CRM. In some solutions the Quick Sizer requires you to specify inwhich application the users work predominantly, for example, on the Quick Sizer questionnaire forFinancials within SAP ERP, it distinguishes between users in controlling and users in financialtransactions. In some user sizings you are requested to specify an activity profile, for example: howmany users have a low, medium or high activity? The activity patterns merely express the number ofscreen changes per user per hour. A highly active user, for example, corresponds to a power user witha think time of 10 seconds. Think time refers to the time between two server events that are triggeredon the front end, for example when the enter key is pressed.

When you’ve entered the user information and choose “calculate result”, you’ll get the followinginformation (per default for each SAP solution):

The required CPU power in SAPS (hardware-independent, see above) Memory in MB Database disk space in GB Disk I/Os per second

For your convenience, there are categories for disk, I/O, and CPU result that indicate whether you arein a small or medium sized environment. As explained above, the initial sizing is only a very roughballpark estimate which is why I would not recommend relying only on a user-based sizing if the resultis higher than 5000 SAPS. User sizing per se is very inaccurate in the sense that it does not accountfor background processes, interfaces, and so on, and therefore the Quick Sizer provides fairly highsizing results as compared to throughput sizing. So, if you happen to be doing both user sizing andthroughput sizing and find that the results differ significantly, you may have specified a user activitythat is too high, some information may be missing in throughput sizing, or the difference may becorrect as is, for example, if the users work slowly with the system.

The Quick Sizer does not offer user sizing for all applications. Process Integration (PI), for example,has no user sizing. As a pass-through engine, it has no dialog load.

3.1.2 Sizing by ThroughputWhen you are a little more familiar with how SAP software represents your business applications,you’re ready for advanced sizing based on throughput numbers. This sizing is usually more accuratefor several reasons. The Quick Sizer contains individual sizings for throughput sizing, thus reflectingthe most common and potentially most load-consuming transactions and business applications forSAP software. The information the Quick Sizer requires from you follows a simple pattern: Number ofobjects (for example, projects, printed documents, sales orders or travel receipts) per year, number ofsub objects (networks, activities or line items) and how many months these data will remain in thedatabase until they are archived. If you enter this information and choose “calculate result“, the QuickSizer renders basic CPU and disk requirements (remember that memory is dominated by users). Thissizing method is called “average sizing” from which you can build on towards a peak sizing.Below find an example for a simple sizing of travel receipts. The sizing element TV-RECEIPT is to sizethe travels that are being processed. The column “Objects” refers the number of travels, and the


column for items refers to the number of receipts. In this case we assume 150,000 travels per year,each with 10 receipts. The data resides on the database for 36 months.

Figure 1: Example for simple average sizing.

The peak sizing method helps you to identify CPU peaks during the busiest day of the year (forexample right before Christmas or year-end closing). You enter the number of objects and sub objectsand specify the time period when these objects are being processed, for example: The payroll of200,000 employees from 2 am to 4 am. If this run coincides with the nightly background run for thematerials requirements planning, the Quick Sizer shows the peak CPU requirement. When we saypeak sizing, we mean the peak over all individual sizing results. If the average sizing for a sizingelement renders 1000 SAPS, and the peak sizing 1200 SAPS, the overall result of the sizing is 1200SAPS. If the peak sizing renders a value that is lower than that of the average sizing (if specified byyou) and both are in the same time slot, the Quick Sizer issues a message.


3.2 Advanced Sizing with the Quick SizerYou can then go on redefining your sizing: For example, you can enter how often an object is changed per year or per peak phase. This

influences the CPU sizing. You may also want to change the average workday. Per default, the Quick Sizer assumes that an

average workday ranges from 9am to 6pm, which you can easily change, thus influencing the CPUresult and average throughput-based I/O sizing.

The Quick Sizer also assumes 220 workdays per year as a default. If you adapt this value to yourneeds, this also influences the CPU result for the average sizing. By the way, the number ofworkdays also influences average throughput-based I/O sizing and user-based disk sizing.

You can extend the average sizing by allowing for multiple averages. For example: in a customersystem, orders are created in SAP CRM, by handhelds and by Interaction Center users. Theorders are transferred to the ERP system for full order processing. By adding lines, you candistinguish between the orders that were originally passed on from the handheld scenario and theInteraction Center. To make this information transparent you can add a short text to each line. TheQuick Sizer will add the averages and calculate the result for you.

One function that, strictly speaking, is not relevant for the sizing calculation is the archiving flag. Ifyou enter this, the Quick Sizer checks whether an archiving object for this sizing element exists.

In the above example with the sizing element TV-RECEIPT, we could assume, that all employees willattend an important business meeting in the end January. For the sake of the exercise, they would allenter their travels on an afternoon. This distinguishes peak from average sizing.

Figure 2: Example for peak sizing

If you use all these functions, you can get a pretty accurate representation of the hardware required torun the business. The types of questions asked in the questionnaire strongly depend on the keyperformance requirements of the different applications. The questionnaires are based on standardperformance measurements SAP regularly carries out in its development departments.

In some cases customer requirements can exceed the scope of the tool to some extent. In thesecases we recommend to use the Quick Sizer as a basis and apply additional methods and guidelineson top of the results. For example, you can use the %display and %change columns to more preciselyreflect your business.

3.3 Quick Sizer for Expert SizingExpert sizing makes the utmost use of the standard functions of the Quick Sizer. Expert sizing is forcustomers whose business requirements surpass the rule of 80/20 (80% of the load is created by 20%of the transactions), first-and-foremost because of custom modifications, system to system dataexchange, customization, and so on.

One standard function of the Quick Sizer that can be exploited for expert sizing is the possibility to setmultiple averages against multiple peaks. The Quick Sizer always checks which sizing method rendersthe higher CPU value, average or peak. Using a function called “ID” for identification, you can specifywhich averages are calculated against which peaks. This is very helpful for complex scenarios, forexample in the retail business or in the example below, where orders come in from very differentsources. The figure below shows you an example. SD-SLS is the SD sizing element “sales orders”, “A”specifies average sizing, “Y” stands for objects per year.


Figure 3: Example for multiple averages against multiple peaks

If you do not enter anything in the ID column, all averages are added and calculated against all peaks,which may blur the result.

Also, you can use rules of thumb mapped to the Quick Sizer to account for special processes. Forexample, there is a rule that says “to account for additional load caused by RFC processing, add 10%load on the sales orders that are transferred to another system”. In this case, you would add anadditional line for peak, enter 10% of the number of orders and add in the short text field “additionalRFC load”.

In principle however, expert sizing can only take place if the customer already has a test system upand running. Then we recommend using standard SAP system monitors to obtain sizing relevantinformation such as CPU time, table size and memory consumed – per business process. If you havethis information you can relate it to the Quick Sizer. For example, you have written your own salesorder application and your measurements show that this is 1.5 times as expensive as the Quick Sizersales order. Then you can simply exploit the functions of the Quick Sizer for your own software byapplying a factor of 1.5.

3.4 Quick Sizer and GoingLiveSAP Support offers the GoingLive Check (GLC), and one of the features of GoingLive (GL) is theplausibility check of the sizing where the Quick Sizer entries and sizing results are checked againstthe performance capacities of the hardware the customer has purchased.

This can be done on the basis of the sizing data filled in the Quick Sizer. In some cases, GLC offersadditional checks if certain business processes are not (yet) included in the Quick Sizer. When youare ready, you can simply set the status of your sizing project in the Quick Sizer to “GoingLive” 23. Nowthere are two different projects with two different owners for one project name. The project owned byyou is “read-only” and the project owned by GLC can be changed by GLC. You yourself are not ableto make modifications to this project until SAP Support has changed the project status to “in processafter GL”, but you can switch in display mode between your project and the project owned andchanged by GLC.

That way, SAP and customer can work together on the hardware plausibility check relying on thesame data.

If you set the project to final, no one can change the project anymore.

2 You have to order the GoingLive Check for your Quick Sizer project.3 Note for secure projects: Changing the status of a secure project to “GoingLive” enables SAPemployees to access this project to be able to do the GoingLive check, not only the participants of theproject access list.


4 Interpreting Quick Sizer ResultsFor reasons of better analysis, the Quick Sizer allows you to analyze sizing results at very differentlevels of detail. Here are the most important ones.

4.1 Different Result LevelsThere are seven different result levels that provide perspectives on the sizing result. The ones thatprovide most important information for analysis purposes are described in detail, the others share onesub chapter.

An important principle of the Quick Sizer is that it calculates the results for each hour over a 24-hourtime period and displays the highest result at any given hour. For example, on sizing project level, theresult displayed is the highest over all solutions. At solution level it shows the highest result for eachsolution. Another principle is that the sizing results for user-based sizing and for throughput-basedsizing are calculated and displayed separately.

4.1.1 Result by SolutionBy default, the Quick Sizer displays the sizing result by sizing method (user and throughput) and bySAP product, for example SAP ERP or SAP NetWeaver (Classic approach). For each solution theQuick Sizer displays the required: CPU power in SAPS (hardware-independent, see above) at a target utilization of 65%, rounded in

units of 100 Memory in MB, rounded in units of 1 GB Database disk space in MB, rounded in units of 1 GB Disk I/Os per second in units of 100 (only for ERP)

For easier analysis, there are also result categories, ranging from small (S) to extra large (XXXL). Thecategories are to provide some estimate what size your project is in relation. XXXL does not reallyindicate a very large sizing, it only means that if you have sizings beyond 48,000 SAPS and/or 1,6TByou should not rely on a tool such as the Quick Sizer alone but check with your hardware provider.

Category Up to … SAPS Up to … GB disk Up to … Disk I/Os per second

XS 2000 100 800

S 8000 250 3000

M 16,000 500 6000

L 24,000 1000 10,000

XL 36,000 1300 14,000

XXL 48,000 1600 18,000

XXXL Contact hardware vendor or SAP for detailed sizing analysis

Table 2: Sizing categories

If you only have a user-based sizing and if this result exceeds category S, you should either perform athroughput sizing or contact your hardware vendor or SAP. If you did both sizing methods and thecategory exceeds XXXL, you should also contact the hardware vendor or SAP for further assistance,because we believe that in the complex world of business applications tools only have a limited scopeof validity.

On all result levels the Quick Sizer provides all available information on the trays ”SAPS” and ”Memoryand disk” in detail, for example the SAPS values for database server and application server, an


information which may become important if you are sizing a multi-tier environment and need to knowhow to split up DB and application resources4.

The results on the tray “SAPS” typically consist at least of the columns, total, DB and App. Dependingon the scenario, additional kinds of CPU requirements may be mentioned.

Column Meaning

…(total) Total displays the highest sum of requirements at a given point of time

DB … Highest DB requirements at any given point of time (individual peak)

App… Highest application requirements at any given point of time (individualpeak), if applicable

Table 3: Results for SAPS and memory

However, it may be that the individual peaks for DB and application server may be at different times,so in order to better configure CPU and memory, the values for DB and App reflect the individualpeaks. As a consequence of this independence, total is not necessarily the sum of the results for DBand App but may be lower. See an example below, where the (rounded) individual results for the CRMserver for DB and App are higher than the total result.

The Quick Sizer results also account for CPU requirements emanating from basic SAP NetWeaverusage types and standalone engines, such as Java Application Server or liveCache.

Figure 4: Example for results on the ‘SAPS’ tray on solution level

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

Aggregation is done the following way: the categories are calculated with the smallest numbers of allsolutions.

For example, if there are only sizings of SAP solution SAP NetWeaver BW (4 TB disk space), onproject level the category will be calculated using BW logic: category L. If there is besides SAPsolution SAP NetWeaver BW (4 TB disk space) also the SAP solution CRM (100 GB disk space),aggregation is done using CRM logic, because there are the smaller numbers: category XXL onproject level.

4 This information is obtained from Standard Application Benchmark runs which simulate typicalbusiness behavior in an optimal environment.


Category Up to … SAPS Up to … GB disk Up to … Disk I/Os per second

XS 6000 500 2000

S 12,000 1000 4000

M 24,000 2500 8000

L 36,000 5000 12,000

XL 48,000 7500 16,000

XXL 72,000 10,000 24,000

XXXL Contact hardware vendor or SAP for detailed sizing analysis

Table 3: Sizing categories for SAP NetWeaver BW

Some notes on offsetsPer default, for 'New SAP Business Solution/Software Component' (with minimal offsets) the grossresults are displayed on the result page for solution level. If you choose 'SAP BusinessSolution/Software Component Extension', net results are displayed. These offsets may be different foreach solution (Note: your choice (New SAP Business Solution/Software Component or 'SAP BusinessSolution/Software Component Extension ) on the project information questionnaire will be saved forthe whole project. Your choice on the result page won’t be saved.)

Things to consider about the different kinds of offsets:

Minimal offsetsMinimal offsets are result thresholds, which act as minimum values. Any result belowthis value is not displayed. Instead, the minimal offset is displayed. For example: if theQuick Sizer calculates 500 SAPS, the minimal threshhold value of 2000 SAPS isdisplayed.If the calculated results are higher than the minimal offsets, the minimal offsets do nothave any influence on the displayed result. For example: if the Quick Sizer calculates5400 SAPS, these 5400 SAPS will be displayed.

Additional offsetsAdditional offsets will always be added to the calculated result.

You can use the print page function to compare the results of the different offset calculations ‘NewSAP Business Solution/Software Component’ and ‘SAP Business Solution/Software ComponentExtension ’. The print page is not updated automatically when you call up another calculation, whichallows you view one calculation on the print page and the other in the Quick Sizer. You can use thefollowing procedure: fill-in your data and choose the calculation button. Per default, the systemdisplays the gross results with minimal offsets. Choose the ‘Print page’ button to display the results inthe print preview mode. Now, choose the ‘SAP Business Solution/Software Component Extension ’button on the result page to recalculate the results. You can now compare the net results on the resultpage with the gross results on the print page by switching between the two screens.

4.1.2 Result at Software Component LevelTo plan your system landscape it is helpful to know the hardware requirements for each softwarecomponent, for example Enterprise Core Component (ECC) or Portal Server. We define softwarecomponent as any separately installable deployment unit.

The notes on offsets in Chapter 4.1.1 apply here, too. Keep in mind that these offsets are different forthe different software components.

Note that we assume one physical application server only. If you plan to install more applicationservers you particularly need to account for that separately, especially regarding memory


requirements.

4.1.3 Results, Statistics and Inputs OverviewThis function is predominantly useful for documenting the sizing project as it contains all the data youentered and all the results of the Quick Sizer. You can make a print view of each result level page and/or input page. This view cannot only be printed, but also saved as an HTML-file. This function is alsohelpful if you want to analyze the sizing data in more detail. More often than you think you can detecterroneous entries by simply doing a plausibility check on the highest CPU or disk contributors. Thisresult level also provides detailed information on the top disk contributors, the table names, theprojected growth after one year and according to the specified residence period, available archivingobjects, and so on.

4.1.4 Other Result Levels “Project” displays the result for all software components. The notes on offsets in Chapter 4.1.1

apply here, too. "Key capabilities" displays the result at questionnaire level. This level does not include offsets. "Sizing elements" displays the result at sizing element level. This level includes the archiving

objects specified for the respective sizing element. It does not include offsets. "Line results and inputs" is helpful for cause-effect analyses of your entries and the respective

results. This level does not include offsets.

4.2 Classic Approach and Combined Approach

Check example project ‘__RESULTS 1 V22 F’ with customer 188213 for an example calculation of thedifferent SAPS results you get for the classic and combined approach.

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

Combined approachThe new combined approach which starts with Quick Sizer version 22 was introduced to calculate totalresults.

Base for understanding of the calculation of the total results are the charts on result level 'Sizingelements' of the online result chart documentation in the classic approach athttp://www.service.sap.com/~sapidb/011000358700001242782010E/level1.htm. Here you can seethat there is not always an user-based and a throughput-based sizing approach existing in a project /Quick Sizer.

With this approach results of disjoint user-based sizing elements are added to the total result forthroughput-based sizings and disjoint throughput-based sizing elements are added to the total resultfor user-based sizings, whereas results for joint sizing elements are only considered in the respectivesizing category (user-based or throughput-based).

Different charts displayed on result levels

Until Quick Sizer version 21 only throughput-based result charts were displayed.

From December 2010 (Quick Sizer version 22), the classic approach displays peak and averagethroughput-based charts on result level 'line results + inputs' also for old Quick Sizer versionsretroactively.

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


Starting with Quick Sizer version 22 there are the following new charts for the classic approach: theuser-based chart for result level 'Key capabilities' and the corresponding throughput-based and user-based charts for result level 'Sizing elements'. This is also retroactively valid for older Quick Sizerversions.

Also starting with Quick Sizer version 22 there are the charts for several result levels of the combinedapproach.

Find an overview about the result level charts in the table below.

Charts of classic approach Charts of combinedNo.ofresultlevel

Result level Throughput-based User-

based

Corres-pondingthrough-put-basedanduser-based

Peakandaveragethrough-put-based

Through-put-basedplususer-basedonly

User-basedplusthroughput-based only

1 Project x x x

2 SAPsolutions

x x x

3 Softwarecomponents

x x x

4 Keycapabilities

x x x x

5 Sizingelements

x x

6 Line results+ inputs

x

7 Results,statistics,inputs

Result levelno:1,2,3,4,5

Resultlevel no:1,2,3,4

Result levelno:1,2,3,4

Table4: Overview about different Quick Sizer result levels

Note that column 'throughput-based' of the classic approach chart was already displayed in formerversions, column 'peak and average throughput-based' will be shown also for older versions, and allother displayed charts are new ones.


4.3 Frequently asked Questions on Quick Sizer Results

Q: There are results for users and throughput. Do I have to add them?

A: Check 4.2 Classic approach and combined approach for comments on the interpretation of user-based and throughput-based sizing results.

Q: Why is a technical upgrade out of scope of the Quick Sizer?

A: Note that there are two types of upgrade: technical and functional.

A technical upgrade is an upgrade from one release to the next higher release of a particular SAPsolution (e.g. SAP R/3 Enterprise SAP ECC 6.0). In this case, significant differences with regard toarchitecture and functionalities are not expected (performance will not change significantly).

Since sizings using the Quick Sizer are based on specific scenarios and contain many assumptions,the Quick Sizer is not the appropriate tool to size technical upgrades. It is much more accurate tomeasure the current resource requirements of the system and adding the requirements of the newrelease. 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).

Find more details within the document “Quick Sizer Best Practices” on the SAP Service Marketplace(http://www.service/sap/com/~sapidb/011000358700000108102008E).

Q: Does the Quick Sizer consider Unicode?A: Yes, but the SAPS result of the Quick Sizer has to be compared with SAPS results from Unicodebenchmarks.

Q: Is the Quick Sizer calculation based on the new SAPS benchmark definition (Subsecondresponse time: The response time for the SD benchmark must be below one second)?

A: Yes, the Quick Sizer result of the Quick Sizer is based on the new benchmarks (since Quick SizerVersion 15). Therefore, for a sizing you have to compare the Quick Sizer results with the results of thenew benchmarks.

Q: I only have user information (3000 ERP users), can I do a user-only sizing?

A: We recommend not to. User-only sizing can be quite treacherous because it doesn't considerbackground activity, system-system communication and other factors.

Q: Is there a report to retrieve the Quick Sizer relevant business data from my productionsystem?

A: The Quick Sizer is meant for an initial estimate only. Once you are live, your own data and systemconfiguration is a much more reliable source for, say, upgrade sizing, than simply relying on SAPstandard. Therefore there is no such report available.

Q: Can I delete sizing projects or can you do it for me?

A: For some reasons Quick Sizer projects cannot be deleted. However, you can set the status of finalprojects to inactive. When you do this, the project will not be displayed if you search for projects.However, if you provide project name and customer number, you can open the project in displaymode.

Q: How do I get the right input data for the Quick Sizer?

A: With the help of input data you should map your business to the Quick Sizer questionnaires to get aresult for a hardware sizing regarding SAPS, memory, and disk.

Now, where do you get the input data from? If you are a big company, you probably have separate ITand user departments. Normally, the request for input data for a sizing will be addressed to the IT

http://www.service/sap/com/~sapidb/011000358700000108102008E).


department firstly. Ideally, the IT department contacts the user department to collect the informationabout the right input data that describes your business. In many cases it is recommended to alsocontact a SAP consultant who has a good business process know-how and knows how to map yourbusiness processes to the corresponding SAP applications. Consultants can give input concerning thescope of the SAP applications and they can improve the communication by translating your customerlanguage into the SAP language. It is very important that the different parties involved in a sizingproject collaborate in a very efficient way from the very beginning on. The challenge in any sizingproject is to obtain sufficient usage information. At the end, you must know that the better your inputdata is the better the Quick Sizer result will be.

Looking for more questions and answers?Over the last couple of years we have received a lot of feedback and questions regarding Quick Sizerusage. As some of these questions are recurring frequently, we have created the document “QuickSizer Best Practices” to help more advanced users use the tool.You find it at service.sap.com/sizing -> Quick Sizer Tool -> Using the Quick Sizer -> Experts. Pleasenote that it is not a compendium of all Quick Sizer characteristics, but basically a collection of answersto questions we have given in the past. It is more comprehensive than the existing FAQ for the QuickSizer which you find at service.sap.com/sizing -> Quick Sizer Tool -> Using the Quick Sizer ->Beginners.


4.4 Additional Functions and Options on the Result ScreenA list with the relevant functions is shown below.

Function Comment

Charts To get a graphic impression of the 24-slope of CPU requirements, youcan use this function. Only available, if you filled in throughput values.

Details To get an impression of the 24-slope of CPU requirements in tableformat, you can use this function. Only available, if you filled inthroughput values.

Table 5: Additional functions on the result screen

5 Overview of Functions and Options in the Quick Sizer

5.1 Documentation and HelpThere are three major sources for documentation and help.

The link “Quick Sizer tool documentation ” leads to this document which explains the basicfunctions of the Quick Sizer.

On each questionnaire, there is a link “How to fill in the questionnaire”, which contains detailedsizing-relevant documentation on each sizing element and sizing guideline implemented in theQuick Sizer. The documentation is geared at explaining the business and technicalassumptions for the sizing elements.

For more information on each sizing element and the column headers there is a tool tip. If youscroll over the words, the long text is displayed.

5.2 Functions and Options in Alphabetical Order

Function Comment% chg. / % dsp. Number of changes or displays to sizing object in %.

One change or display equals 100 %, so you have to enter‘100’ in the theses columns, if the objects are displayed andchanged once or you have to enter ‘50’ in these columns, ifhalf of the objects are displayed and changed.Note that the change or display of an object is as expensiveas the creation of the object for CPU resource consumption.Check example project ‘__%DSP/% CHG V1 F’ on resultlevel ‘Line results + inputs’: 433 SAPS are caused bycreation, 433 SAPS are caused by one change, and 433SAPS are caused by one display, that means 1298 SAPS intotal.

Avg. workday and peak load Per default, the average workday is set from 9 am (9:00) to 6pm (18:00). For each questionnaire, you can modify thesedaily working hours.The peak load default is set from 12:00-13:00. You can eithermodify the default for the questionnaire to change initial lines(that means already filled peak data are not overwritten) ormodify the peak times in each line separately.(see also “Workdays”)

Check input If you entered you data, you can use this button to checkwhether there are input errors. Either you get a message thatthere are no input errors detected or error messages.


Clear Questionnaire This button clears all information entered in a questionnaire.The user gets no confirmation popup. If you clear the contentof a questionnaire by accident, you can leave the projectusing the ‘EXIT’ – button and enter it again, because theclearance does not include an autosave.

Copy function in SAP NetWeaver BW In the table for definition of InfoCubes of the SAP NetWeaverBW questionnaire you find this function to copy marked lineswith input.This can be used if the size of your InfoCube exceeds thesize of an InfoCube that can be filled in Quick Sizer.

Create Projects with Reference If you want to create variations of existing projects, you canuse this function on the entry screen of the Quick Sizer.Simply enter a new project name and the Quick Sizer createsa new project with the data and project version of thereference project. If you use a reference project which hasnot the current version, you get some information messagesconcerning this. If you are copying a project which wascreated more than 4 Quick sizer versions ago, you receivewarning messages instead to let you know that the QuickSizer version of your project is outdated by more than oneyear.When the new project is opened, the project informationquestionnaire is shown.

Disclaimer The link opens the disclaimer you’ve had to accept the firsttime you used the Quick Sizer.

Documentation and Help See sub-chapter 5.1 on documentation and help

Exit The exit function takes you back to the start screen.Note: if you use the exit button, changes after the last explicitsave (using the “Save” button) or implicit save (changing aquestionnaire or calculating results) will not be considered.

Feedback You can use this function to send us your feedback about theQuick Sizer tool anytime. Furthermore, this anonymoussurvey will be conducted automatically for every version on aregular basis.

Hardware vendors The link opens an HTML page with links to hardware vendorswho you may contact for a sizing proposal. All you need is toprovide them with the customer number and the projectname.

Insert/Clear You can capture multiple different sizings for the same sizingelement by using the insert function. With the clear functionyou either delete additional lines or clear the entries.


Limit User Access If you set the flag “Limit user access”, only you as projectowner can grant other persons access to the project data.Enter the user-IDs of these persons and choose the “Adduser” button. To delete persons from your access list, set thecursor on the user-ID in the drop-down list box and choose”Delete user”.If you uncheck the flag, your project can be accessed byeverybody who knows the customer number and the projectname.In your project overview list protected projects are marked.Note: Changing the status of a secure project to “GoingLive”enables SAP employees to access this project to be able todo the GoingLive check, not only the participants of theproject access list.

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

Navigation The navigation tree displays all sizing questionnaires andadditional guidelines, if applicable. The icons to the left show,if a questionnaire has been filled in, if there are errors (redlight), and which one is currently being displayed (“bulb”).

Owner Per default, the owner is the person who has created thesizing project, i.e. “customer”. When a project status hasbeen set to “GoingLive”, the owner turns into “GoingLive”.See also the section on Quick Sizer and GoingLive in chapter3.4.

OSM If you choose the sizing result level “Sizing elements” (seealso chapter 4.1.4) some sizing elements are marked in the“OSM” column, which means that they are also sized inanother sizing method. For example, on the SAP ERPProduct Dev. & Execution questionnaire the sizing elementsALM-USER for user-based sizing and ALM-PM forthroughput-based sizing.

Print Page When you choose Print, the Quick Sizer generates a pagethat can be downloaded or printed.For the most optimal printout choose the following settings inyour browser, e.g. MS Internet Explorer:View -> Text Size -> MediumFile -> Page Setup -> Orientation -> Landscape -> Paper ->A4

Project Information This optional questionnaire has been designed by thehardware vendors so that customers can already providesome additional information. The input has no influence oncalculation.

Save There are two methods for saving your input data: Manually, by using the save button Automatically, by navigating from one questionnaire

to another or by calculating results

Search for Project Names If you have forgotten a project name, choose the “Show myprojects” button to get a list of all of your projects. Note: Thisfunction is restricted to projects you have been working on.


Search Function The search function is version dependent, which means thatit is available after you have opened a project. The searchtakes place within the version of the project you have openedand within the current Quick Sizer version. Parts of thenavigation tree which are not found in the project version butin the current Quick Sizer version will be presented with a(New) at the beginning. You cannot access these elementsdirectly by clicking on them. To access these elements youhave to open a project with the current Quick Sizer version.To access elements that are available in the project versionclick on them in the navigation tree.

The program searches for your search string across thevisible and invisible parts of the Quick Sizer.(for examplesearch string fields). The results are displayed in thenavigation tree.

All result lines are marked with an information icon. If the string is found in the visible parts, the search

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

entire result line will be presented bold, enlarged, andin italics.

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

If you check the flag “Match whole word”, only words thatexactly match your search criteria are displayed. Forexample, if you enter “HR” without the flag, you also get “…synchronized …” in your search results. If you check the flag“Match whole word”, these kinds of results will not bedisplayed.

You can also choose between “Phrase”, “Or” or “And”: If you choose “Phrase”, you only get the results that

contain the exact search string. For example, if yoursearch string is “Sales & Service”, you get resultssuch as “Sales & Service”.

If you choose “Or”, all the returned results containone or more words of your search string. Forexample, if you search for “Sales Service” theprogram returns all results that contain either sales orservice or both.

If you choose ”And”, only the results that contain allwords in your search string are returned. Forexample, if you search for “Sales Service”, theprogram only returns the results that contain bothwords.

Short Text You can choose between long and short text. If you chooselong text besides the abbreviation for the sizing element,also a longer short text for the sizing element is displayed.This adjustment will be kept if you change the questionnaire.

Show Examples If you choose this button, you get a list of available exampleprojects for Quick Sizer questionnaires.


Status Once you have entered and saved data in a sizing project,the status is “in progress”. You can change it to GoingLive orto final. See also the section on Quick Sizer and GoingLive.

Use Default Values With this button you reset the default values after you hadoverwritten them. Note, that additional made inputs will not beskipped and have to be adjusted possibly.If you want to have the original inputs, mark the input line,choose “Delete/Clear” and then “Use Default Values”.

Workdays Per default the value is set to 220, but you can specify anynumber of workdays between 150 and 365. The number ofworkdays influences the disk size of user sizing, the CPUrequirements of average throughput sizing and average I/Othroughput sizing.(see also “Avg. workday and peak load”)

Table 6: Options and functions in alphabetical order


6 Some Tips on Checking the Quality of Sizing Projects

6.1 Analyzing the ResultsYou can analyze Quick Sizer results at different levels. The most obvious possibility to check, if thesizing makes sense at all is by analyzing the ratio of the result for user sizing and for throughputsizing.

You can take a look at the below described sizings at service.sap.com/quicksizing, customer number188213, project name DK_RG_EXAMPLE.

Compare results for user and for throughput sizingRecently, a customer created a sizing project, where the results were about 62,000 SAPS for usersizing and 2600 SAPS for throughput sizing. The customer was wondering what result to take as asizing, as the data had come from the application department. Cross-check business information: The data entered was 2000 medium active users and 2 million

sales order items in CRM sales. Make simple calculations: If you assume an average number of 220 workdays per year, every day

roughly 9000 orders are being created, which would mean in turn, 4 per user per day. Interpret: Medium activity users have an assumed 30 seconds think time between hitting the enter

key (think time). If they are really medium active users, what else do they do? Conclusion: Check with the application department, if the users are perhaps named users, if the

information on 2 million sales orders per year is correct, or if there are additional sales activitiesthat have not been accounted for.

It happens fairly often, that user sizing differs from throughput sizing. In no way should you add thesizing results. There may be good reasons for different results, in which case you must decide foryourself, if you trust the results. For example, you are in a retail business with a few users in sales whocapture sales data, but a huge amount of sales orders coming in from various department stores viainterfaces so that you might have a huge result for throughput sizing and a fairly small one for usersizing.

Often, the user sizing result is slightly higher in terms of CPU and disk. This is caused by the fact thatuser sizing reflects a more scenario-oriented approach whereas throughput sizing tends to reflectbusiness objects. For example, sometimes only sales orders are entered without specifying the follow-on objects as well.

Unreasonably high sizing result

Another customer created a sizing project and was proposed a 53 GB memory server when all theyhad available was an 8 GB server which did the job perfectly well for a legacy system. The customerwanted to size Demand Planning and multiplied all location products with all locations available andentered this data into the Quick Sizer. In real life, only a fraction of the products were sold in alllocations. Also, only the active characteristic combinations are relevant for sizing.

The documentation ‘How to fill in the questionnaire’ on each questionnaire explains which businessinformation is relevant for the sizing.


Misinterpreting peak sizingThe idea of the peak sizing method is to help you identify CPU peaks during the busiest business timeof the year (for example right before Christmas or year-end closing) or background jobs. You enter thenumber of objects and sub objects and specify the time period when these objects are beingprocessed. For example: You have two batch job peaks for controlling and business accountingdocuments (CO and FIN-BAC), which have to be processed within one hour (1 pm to 2 pm). Theycreate 600 SAPS each. You also have a certain number of controlling and business accountingdocuments (CO and FIN-BAC) that have to be processed during a year (average sizing) with a 9 am to6 pm workday. They create 500 SAPS each. The Quick Sizer shows the peak CPU requirement,because the highest value at a given point in time is taken as the result. When we say peak sizing, wemean the peak over all individual sizing results. If the average sizing for these two sizing elementsrenders 1000 SAPS, and the peak sizing is 1200 SAPS, the overall result of the sizing is 1200 SAPS.If the peak sizing renders a value below the average sizing, the Quick Sizer issues a message.

Dominating sizing elements

In another example a customer had a very high sizing result in which one sizing element was clearlydominating the others. The customer had a number of different online and background activities inproduction execution. The majority of the processes ran between 10 am and 6 pm, with one hugebatch job scheduled for 5pm. Moving the job by one hour to 6pm resulted in nearly half therequirements. By analyzing the Quick Sizer results according to the time lines, you can actually planbatch schedules. Needless to say, any schedule changes have to be in line with your businessrequirements, which in some cases are very strict and don’t even allow a shift of half an hour.

If your disk space requirement is unusually high, your retention times may be too long. However, oftenthese times cannot be changed, because they are based on laws and regulations.

6.2 Assessing the InputThe above assessment of the results had a more technical perspective. But even from an applicationperspective you can check, if the entries make sense. One customer said they had 2000 users in a particular HR application (personnel administration)

at medium to high activity. The customer had a workforce of 40,000 employees so that 5% of thetotal workforce worked in HR administration with a medium to high activity. This entry seemshighly questionable.

In another case a customer entered 10 million sales orders, but only 2 million goods movementsand 2 million deliveries. Is the ratio coherent? One would assume that there is a similar number ofsales orders and deliveries. In this particular case financials documents where missing altogether.Of course, there may be good reasons for mismatching entries, particularly, when there are legacysystems or third-party products in use, but very often this is not the case.

7 FeedbackFeedback is very welcome; please send it to Dagmar Kirsamer ([email protected]),Performance & Scalability.

mailto:[email protected]

architecture difference between nw 7.0 and 7.1

Documents