configuration and maintenance steps for server side

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

© 2010 SAP AG 1

Configuration and Maintenance

Steps for Server Side Performance

Benchmarking

Applies to:

The guidelines specified in this document are release independent. For more information, visit the Mobile homepage.

Summary

This document provides guidelines to configure and maintain the DOE (Data Orchestration Engine) for performance benchmarking.

Author: Akila Sangili

Company: SAP Labs India Pvt.Ltd

Created on: 15 Nov 2010

Author Bio

Akila Sangili is working in the Engineering Services area for NetWeaver Mobile team at SAP Labs India Pvt. Ltd.

http://www.sdn.sap.com/irj/sdn/mobile


Configuration and Maintenance Steps for Server Side Performance Benchmarking


© 2010 SAP AG 2

Table of Contents

Introduction ......................................................................................................................................................... 3

Maintain/Configure Application Server ............................................................................................................... 3

Validating component version ......................................................................................................................... 3

Validation of supporting component notes if any ............................................................................................ 4

Validation of System Parameters .................................................................................................................... 5

For Buffer and Memory ................................................................................................................................... 5

Validation of Dialog Work Process .................................................................................................................. 8

Check on CPU , Memory Utilization .............................................................................................................. 10

Maintain/Configure Database ........................................................................................................................... 10

Database Locks ............................................................................................................................................ 11

Table Analysis ............................................................................................................................................... 12

Setting Memory for Database ....................................................................................................................... 13

Data files and logs of database ..................................................................................................................... 14

Data Cache and its hit ratio ........................................................................................................................... 15

Maintain/Configure Data Orchestration Engine ................................................................................................ 15

Backend Configuration .................................................................................................................................. 16

DOE Configuration ........................................................................................................................................ 16

Monitoring and Validating the test execution in DOE ....................................................................................... 18

Related Content ................................................................................................................................................ 20

Copyright........................................................................................................................................................... 21



© 2010 SAP AG 3

Introduction

The Data Orchestration Engine has to be configured and maintained for performance measurements if the expected throughput has to be achieved with the determined hardware requirements based on sizing.

Maintenance and configuration has following steps

Maintain/Configure Application Server

Maintain/Configure Database

Maintain/Configure Data Orchestration Engine

Below content are the guided procedures to perform the above mentioned steps with screenshots wherever applicable with NetWeaver Mobile 7.1 as reference release.

Maintain/Configure Application Server

Validating component version

Component Version can be checked Under Status of System menu.



© 2010 SAP AG 4

Click on the component information button.

Component Information provides both the release and the service pack information.

Validation of supporting component notes if any

For the particular Release and the service pack considered for testing, check if any consolidated notes are available and ensure that are available in the system.

Notes can be found at http://service.sap.com/notes

http://service.sap.com/notes



© 2010 SAP AG 5

Validation of System Parameters

For Buffer and Memory

Transaction Code : ST02

Use the tcode ST02 to validate the buffer and memory configurations before starting the measurements.

High number of swaps beyond the limit which are marked as red are indication of poor performance.

Buffer Hit Ratio and Number of swaps for the buffer can be tuned by changing the relevant memory parameter according to the available physical memory. Available physical memory can be found by using tcode ST06. The associated parameter can be determined by double clicking the relevant entry and by clicking the current parameters.



© 2010 SAP AG 8

Validation of Dialog Work Process

Use Process Overview SM50 to find the current available number of work processes.DIA (Dialog) Work processes are used for executing dialog steps in user transactions. In SM50, Utilization of work process is shown as Average Workload = (X/Y/Z) that means X Processes were used in the last minute, Y Processes were used in the last 5 minutes and Z processes in the last 15 minutes.

Number of dialog work processes should be at least equal to the number of CPU cores in the system. In a system with 4 CPU cores, dialog work processes can be configured to 12.

Configure the trace level of dialog work processes to 1 to trace only when there is error. Trace levels can be configured by using the Administration menu in SM50.



© 2010 SAP AG 9

Active Components will take you to the trace level of components, change and save the setting.



© 2010 SAP AG 10

Check on CPU , Memory Utilization

Use transaction code st06 to find the Number of CPUs , CPU Utilization and the availability of physical memory.

Maintain/Configure Database

Note: The screenshots shown below are based on MSSQL database.

Use transaction code db02 to get the details related to Database.

Transaction code db02 points you to the space overview of the database in terms of data and logs.



© 2010 SAP AG 11

Database Locks

During the execution of tests, there could be delay in processing the database requests which could be due to the locks happened in the database.

Check Locks under Performance view.



© 2010 SAP AG 12

Table Analysis

Table analysis in terms of its size, rows , indexes and the statistics can be checked under Single Table Analysis under Space by specifying the table name.

If the performance is affected due to huge data in some tables, then to identify the same check Fastest Growing Tables and Largest Tables under space view.



© 2010 SAP AG 13

Setting Memory for Database

65% of the total memory can be allocated to the Database. For Example If we have a RAM size of 32 GB, then 22 GB can be allocated to Database. Memory Mode should be set to Fixed and not Auto in order to avoid the memory problem.

The Current memory allocated and the memory setting for the database can be checked under overview of performance view.

The configuration parameters relevant to the memory settings are max server memory (MB) and min server memory (MB) which are available under configuration options of Configuration View. To keep the memory setting to be fixed, configure the parameters max server memory and the min server memory to the same value.



© 2010 SAP AG 14

Data files and logs of database

Avoid storing the data files and logs of the database on the same drive to improve the I/O Performance and the commit operation. Refer files under overview of space tree view to locate the drives where the logs and the data files are stored.



© 2010 SAP AG 15

Data Cache and its hit ratio

Data Cache hit ratio above 95% will lead to better performance as the data and the index pages can be read from the buffer instead from the disk. If its below 95% check for the data cache size and increase the same.

Data cache size and hit ratio can be checked under overview of Performance view.

Maintain/Configure Data Orchestration Engine

Refer to the below mentioned link for configuring and maintain the Data Orchestration Engine in general.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0770791-8acb-2c10-3194-8887bc0b730f?QuickLink=index&overridelayout=true

Below are the steps which explains the configuration on the Data Orchestration Engine for tuning performance.

Configuration includes both DOE and the Backend configuration.





© 2010 SAP AG 16

Backend Configuration

Parameters BACKEND_PACKAGE_SIZE and BACKEND_MAX_QUEUES are tuned with respect to the Backend.

Recommended value for BACKEND_PACKAGE_SIZE :20000 - 1000

Recommended Value for BACKEND_MAX_QUEUES : Number of CPU cores + 1

Backend configuration can be achieved via Administration and monitoring portal of Data Orchestration Engine.

DOE Configuration

Parameters CDS_READ_PACK_SIZE_FOR_EXT, CLIENT_PACKAGE_SIZE, DOE_PACKAGE_SIZE and QUEUESIZE are tuned with respect to the DOE.

Recommended value for CDS_READ_PACK_SIZE_FOR_EXT : 1000

Recommended value for CLIENT_PACKAGE_SIZE for Laptop : 1000

Recommended value for DOE_PACKAGE_SIZE : 200

Recommended value for QUEUESIZE : Number of CPU Cores + 1



© 2010 SAP AG 17

DOE configuration can be achieved via Administration and monitoring portal of Data Orchestration Engine.

Please refer SAP Note – 1155550 for more explanation about the Backend and the DOE Parameters mentioned above.



© 2010 SAP AG 18

Monitoring and Validating the test execution in DOE

The server side scenarios like Initial load, delta load, Rule evaluation and Extracts are processed in queues.

Hence these scenarios can be monitored via queue tracking under Monitoring of DOE Administration and Monitoring portal.

Use transaction STAD to determine the CPU time, time spent in DB, RFC , the number of database requests and the memory utilization for the respective scenario by specifying the relevant user , date and time with which the scenario was executed.

Use transaction ST05 to trace the SQL statements and the RFCs.

Note: Traces to be switched on only for analysis and not on the productive environment.

To trace the activities/SQL statements fired by a particular user, use the Activate trace with filter option and specify the user name with which the scenario was executed.



© 2010 SAP AG 19

Traces can be switched off by selecting the Deactivate trace and it should be saved/displayed for analysis.

Display the saved trace and summarize the trace by SQL statements to identify the costlier statements.



© 2010 SAP AG 20

Related Content

The below link details about sizing the load scenario using STAD. The usage of STAD explained in the below document can be applied for all the server side scenarios.

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90372c41-a1cf-2c10-7287-d9ff7b2cd67b

For more information, visit the Mobile homepage.

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90372c41-a1cf-2c10-7287-d9ff7b2cd67b




© 2010 SAP AG 21

Copyright

© Copyright 2010 SAP AG. 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 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, 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.

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.

SAP, R/3, 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 AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

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 AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty 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 express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

configuration and maintenance steps for server side

Documents