Sizing Meeting

November 2006

Performance, Data Management &

Scalability
SAP AG
 Agenda

1) Quick Sizer News

2) Suggestion for memory sizing guideline

3) Methods of sizing validation

4) Miscellaneous

© SAP AG 2006, Title of Presentation / Speaker Name / 2

 Next GoLive (Version 6): December 18

Heads up for most important changes

Unicode will be included by default
New I/O sizing guideline

Some updated sizing guidelines

© SAP AG 2006, Title of Presentation / Speaker Name / 3

 Quick Sizer Statistics

All All Projects Different Customer

Projects* Except 12345 Numbers
and 188213
Until Oct. 2006 12631 11904 4340

Until Sept. 2006 11694 11024 4132

Total 2005** 4050 3822 1870

Below a list that includes all projects with status GoingLive

Until Sept. 2006 2823 2787 1893

Until Sept. 2006 2621 2577 1784

Total 2005** 994 980 753

* Some restrictions apply (input data correct, minimum 2 lines filled in)
** Since start of QS in July 2005

© SAP AG 2006, Title of Presentation / Speaker Name / 4

 Agenda

1) Quick Sizer News

2) Suggestion for memory sizing guideline

3) Methods of sizing validation

4) Miscellaneous

© SAP AG 2006, Title of Presentation / Speaker Name / 5

 Handling Memory Sizing in QS

Currently
User sizing: user contexts plus offset
Throughput:
– General: no memory sizing
– Exceptions: SCM, BW, XI, TREX

Possibilities
As-is: correct net calculation
Tie memory to CPU result (per xxx SAPS xxx GB memory)
– Users
- Adv: higher result
- Disadv: heuristic; CPU result usually very high
– Throughput – all except above exceptions
- Adv: memory sizing in existance
- Disadv: heuristic

© SAP AG 2006, Title of Presentation / Speaker Name / 6

 Agenda

1) Quick Sizer News

2) Suggestion for memory sizing guideline

3) Methods of sizing validation

4) Miscellaneous

© SAP AG 2006, Title of Presentation / Speaker Name / 7

 Methods for Sizing Validation

Logical checks on inputs in standard tools

Phased rollout
20% of the planned volume to go live relate actual usage to planned
volume

Performance load tests

Baseline tests
Full-blown volume tests

Use the Quick Sizer for initial sizing only

Do not use the Quick Sizer for retro calculation!
Once you have finalized Customizing, your own data is the best basis
for a sizing

© SAP AG 2006, Title of Presentation / Speaker Name / 8

 Input Analysis in Quick Sizer: Check Meaningfulness of Inputs

In many sizing projects, the discrepancy between the

result of user sizing and throughput sizing is extremely
large

© SAP AG 2006, Title of Presentation / Speaker Name / 9

 Input Analysis: Check Meaningfulness of Inputs (2/2)

On result level ”Line results and inputs”, you can make

checks on result versus input values
Do 1000 users of medium activity only create 10,000 activities in 10 hours?

These logical checks can be quite helpful

Exceptions: batch-driven processing ☺
© SAP AG 2006, Title of Presentation / Speaker Name / 10
 Optimizing Batch Processing Times

Moving processing times may decrease overall load

Overall result: 19,300 SAPS (project level)

More detailed analysis reveals overlapping processes (solution level)

Individual results and chart

reveal optimization potential

© SAP AG 2006, Title of Presentation / Speaker Name / 11

 Overview of Fastest Growing Tables

© SAP AG 2006, Title of Presentation / Speaker Name / 12

 Methods of Quick Sizer Validation

CPU analysis (over the last month)

Monitor CPU utilization (ST06)
– With the current hardware, net SAPS can be obtained and related to predicted
SAPS under 65% utilization
Analyze top consumers (sub applications/transactions)
– Compare with Quick Sizer prediction (level of line item or sizing element)

Memory
ST06 delivers system-wide memory consumption
ST07 delivers concurrent users in various activity patterns c.f. with
QS entries

Disk
From DB02 obtain fastest growing tables and indexes and compare with
statistics table in QS

© SAP AG 2006, Title of Presentation / Speaker Name / 13

 Finding out the Number and Size of Business Objects

Example
Transaction DB15 "Tables and Archiving Objects"
– Which tables belong to specifc archiving objects
– With the table names, SE16 delivers the number of entries, i.e. the number of
objects

© SAP AG 2006, Title of Presentation / Speaker Name / 14

 Reflections on High Volume / Load Tests
Opportunities
Verification of scalable software
and system infrastructure
– Load balancing
– Parallel processing
– Locking behavior
– System tuning and parameterization
– Bottleneck analysis for infrastructure
– Fail-over, back-up and disaster
recovery strategies
– Monitoring and system administration,
calibration of thresholds
Robustness
– No deadlocks
– Data consistency
– Possible performance degradation in
overload situations
Verification of sizing models
Identification of memory leaks
(especially with Java applications)
© SAP AG 2006, Title of Presentation / Speaker Name / 15
Threats
Projects
– Across organizational structures
– Get the right people on the project
(knowledge and expertise)
– High planning effort to simulate proper
system behavior
Additional expenses for infrastructure /
hardware
– Dedicated test systems, the more
complex, the more servers
Single analysis including tracing and
profiling still has to be done
High degree of discipline required
– Complexity of test cases and their setup
– Changes to test case / process
 Agenda

1) Quick Sizer News

2) Suggestion for memory sizing guideline

3) Methods of sizing validation

4) Miscellaneous

© SAP AG 2006, Title of Presentation / Speaker Name / 16

 Next Meeting: December 5

Planned agenda
Quick Sizer status
Sizing cProjects
Miscellaneous

Any suggestions from you?

© SAP AG 2006, Title of Presentation / Speaker Name / 17

 Copyright 2006 SAP AG. Alle Rechte vorbehalten

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The
information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,
zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation
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.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG 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.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for
any purpose without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains
only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular
course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP
at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the
information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind,
either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-
infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may
result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access
through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty
whatsoever relating to third-party Web pages

© SAP AG 2006, Title of Presentation / Speaker Name / 18