ALM124

7/28/2019 ALM124

1/29

ALM124

Effective Scalability and Load Testing forSAP ApplicationsGaneshmoorthy DuraisamyNovember, 2012

7/28/2019 ALM124

2/29

2012 SAP AG. All rights reserved.

Disclaimer

This presentation outlines our general product direction and should not be relied on

purchase decision. This presentation is not subject to your license agreement or anywith SAP. SAP has no obligation to pursue any course of business outlined in this pr

develop or release any functionality mentioned in this presentation. This presentatio

strategy and possible future developments are subject to change and may be chang

time for any reason without notice. This document is provided without a warranty of a

express or implied, including but not limited to, the implied warranties of merchantab

particular purpose, or non-infringement. SAP assumes no responsibility for errors or

document, except if such damages were caused by SAP intentionally or grossly neg

7/28/2019 ALM124

3/29


Agenda

Introduction

KPIs and Scalability of SAP Software Architecture

Frontend

Backend Application Layer

Backend Database Layer

Single User Performance Testing

Load Testing

Monitoring and Analysis

7/28/2019 ALM124

4/29


Likely additional users, higher

throughput

Likely legacy/third party software

Higher level of integration

More load on interfaces

Less controlled

Possible Evolvement of Large Systems

"home-made" growth

Increasing user numbers, higher

throughput

Increasing number of applications

Rather controlled

Same software, perhaps template

approach

Organic Growth Mergers / Acquisitions

Some Characteristics for Large Systems

Need to consolid

Users connect ov

"Central system"

One database

One client

All processes are

Application ope

Downtimes, pla

Single G

"Large" systems can be described with very different characterist

7/28/2019 ALM124

5/29 2012 SAP AG. All rights reserved.

Feasibility of Large Systems

Feasibility Custom codin

Can SAP software payroll 3,000,000 employees

and pensioners in less than three hours?Can SAP software fulfill our requirements

concerning 30 million business partners?Can SAP software meet the service levelagreement of < 1 sec server response time in

our corporate portal?Can SAP software handle database tables of

more than 1.5 TB and what are the implications?

The most common frequency

problems is quarterly or mont

code the number one culprit.

ERP Terabyte Club - Critica

Research at customers indica

performance pain points (i.e.

times, long-running jobs) wercoding

[...]

Furthermore, studies reveal t

custom-coded functionality is

of the standard applications o

used

7/28/2019 ALM124


Load and Scalability Testing

Load testing is the process of putting demand on a system or

device and measuring its response. It is performed todetermine a systems behavior under both normal and

anticipated peak load conditions and helps to identify the

maximum operating capacity of an application as well as

bottlenecks.

Scalability Testing is focused on understanding how an

application scales as it is deployed on larger systems and/or

more systems or as more load is applied to it.

7/28/2019 ALM124


Agenda

Introduction


Frontend




Load Testing


7/28/2019 ALM124


Performance, Response Time, and Throughput

Possible performance metrics:

Response time user experience / productivity

System throughput business requirement, system

resource consumption, IT budget

Good performance:

If the performance metrics match the business

requirements or Service Level Agreements

(expectation handling)

Several parts that constitute the end-to-end (E2E)

response time:

Server response time

Network time

Frontend time

Application Server

Application Server(s)

Database

Web Server(s)

Browser

7/28/2019 ALM124


Agenda

Introduction


Frontend




Load Testing


7/28/2019 ALM124


Thousands

Terabytes oHigh throug

Large objec

Globally dis

Hardware a

Many serve

Dimensions ofinternal and external scalability Effects of scalability

Dimensions and Effects of Scalability

7/28/2019 ALM124

11/29


Ensure Linear Scalability in Resource Consumption

Processing time

Linear behavior can be best checked with varying

object numbers and sizes, and varying number ofconcurrent users

Memory consumptio

Efficient data design and release no

memory as early as possibleUsing short living transactions / ses

easily eleminate memory leaks

Extensive garbage collection activit

the performance and scalability sig

Number of processed units / conc. users

CPU utilization(%)

increases linearly

to 100%

10,000

Time

100

Javaheapusag

e

CPU consumption per processed unit

/ conc. user remains constant

Response time

behaves according

to queuing theory

7/28/2019 ALM124

12/29


Agenda

Introduction


Frontend




Load TestingMonitoring and Analysis

7/28/2019 ALM124

13/29


DB LayerKPIs and its effects

Index Design

All frequently executed database accesses (selects, updates and deletes) must be supportedA highly modified table, i.e., a table with many INSERT or UPDATE or DELETE operations sh

many indexes, The indexes must be maintained by the DBMS.

The more columns an index has, the higher the chance that an UPDATE will affect one of the

More than 10 msec in the column Minimum Time / Recordin Performance Trace (ST05) sugg

indexing use explain function

Identical SelectsMake sure there are not much identical selects to DB layer

Buffers and Caches

Accessing from DB is 10 times slower than Application buffer, so make sure we use the buffer

7/28/2019 ALM124

14/29


Agenda

Introduction


Frontend





7/28/2019 ALM124

15/29


Single User

Single User Test

Small test system(QA, development), one user

Volume Test

Test with big data volumes

Quality and implic

persistence layer

Linear resource c

Parallel processin

balancing

Memory usage an

Analyze & measure

scalable behavior

Performance

for high volume

Verify assumptions

7/28/2019 ALM124

16/29


Testing for Linear Resource Consumption

To test whether the solution is scalable, perform linearity tests.

Scalability tests are basically a repeatable pattern for (example):

Scalability with an increasing number of objects 1 object, five line items

10 objects, five line items

100 objects, five line items

Scalability with an increasing number of line items 1 object, 1 line item

1 object, 10 line items

1 object, 100 line items

The results of these controlled tests can be analyzed to determine if there are any pe

bottlenecks

7/28/2019 ALM124

17/29

7/28/2019 ALM124

18/29


Agenda

Introduction


Frontend





7/28/2019 ALM124

19/29


Load Testing

Load Testing Objectives

Is the Application Scalable? Is the Application Stable?

When does the System break?

Load Testing

7/28/2019 ALM124

20/29


Load Testing - Scripting Best Practices

Right think time

Right Data

Correlating Dynamic values

Right error handling

Right Checks

Below are the scripting best practices which needs to be considered irrespective of t

to simulate real world load and test the application.

7/28/2019 ALM124

21/29

7/28/2019 ALM124

22/29


Agenda

Introduction


Frontend



Singe User Performance Testing


7/28/2019 ALM124

23/29

7/28/2019 ALM124

24/29


Server Level Monitors

UNIX Monitors

Network Delay Monitor

Clients Internet/Intranet Appservers

Windows Monitors

7/28/2019 ALM124

25/29


Application Level Monitors SAP Extended Diagnostics

SAP Extended Diagnostics by CA Wily (CA Wily Introscope) is an enterprise application p

management solution that enables you to monitor complex applications 24x7and detect proble

A li ti L l M it

7/28/2019 ALM124

26/29


Application Level MonitorsWhat Introscope can do?

Performs end to end Application Management

Monitors load, requests, Threads, sessions and application system resources

Enables Problem root cause diagnosis

Isolates a problem and pinpoints to the tier or Component Level

Which Method/Class is causing a bottleneck?

Is our problem in the code, the database, or the backend?

How many requests to a specific service failed during the last hour?

How long did a specific request take?

Introscope can quickly and reliably answer these questions and determine where

7/28/2019 ALM124

27/29


Analysis - Tools

7/28/2019 ALM124

28/29


Further Information

http://service.sap.com/performance

Information about load and volume tests: procedure, examples

Recommendations for system tuning (http://service.sap.com/performance -->

Guidelines for efficient programming (http://service.sap.com/performance -->

SAP Extended Diagnostics by CA Wily: http://www.sap.com/lines-of-busines

diagnostics

SAP Service Marketplace
http://service.sap.com/performancehttp://www.sap.com/education/https://websmp209.sap-ag.de/~sapidb/011000358700005304132005Ehttp://service.sap.com/performancehttp://service.sap.com/performancehttp://www.sap.com/lines-of-business/it/extended-diagnosticshttp://www.sap.com/lines-of-business/it/extended-diagnosticshttp://www.sap.com/lines-of-business/it/extended-diagnosticshttp://www.sap.com/lines-of-business/it/extended-diagnosticshttp://www.sap.com/lines-of-business/it/extended-diagnosticshttp://www.sap.com/lines-of-business/it/extended-diagnosticshttp://www.sap.com/lines-of-business/it/extended-diagnosticshttp://www.sap.com/lines-of-business/it/extended-diagnosticshttp://www.sap.com/lines-of-business/it/extended-diagnosticshttp://service.sap.com/performancehttp://service.sap.com/performancehttps://websmp209.sap-ag.de/~sapidb/011000358700005304132005Ehttp://www.sap.com/education/http://service.sap.com/performancehttp://service.sap.com/performance

7/28/2019 ALM124

29/29

FeedbackPlease complete your session evaluation for ALM124

For additional queries [email protected]

Thanks for attending this SAP TechEd s

ALM124

Documents

Transcript of ALM124