Performance Tuning

Methodology Overview

Copyright Oracle Corporation, 2004. All rights reserved.

 Agenda

Performance Tuning Methodology

Tuning as an iterative approach
Communication Strategy
Configuration Data gathering
Performance Monitoring
Performance Testing
Problem Identification / Resolution

1-2 Copyright Oracle Corporation, 2004. All rights reserved.

 Tuning as an Iterative Approach

Performance Tuning does not have a

predetermined path
It is usually an iterative approach
Not all problems are known at the beginning
Resolution of one problem may reveal another
Process could proceed indefinitely
Need agreed upon performance targets / metrics

1-3 Copyright Oracle Corporation, 2004. All rights reserved.

 Communication Plan

Effective communication between ORCL and

customer is key to successful engagement
Use of Scorecard is an integral part of that Plan
Agree upon success criteria / exit strategy
When is the work done?
Summarize recommendations made / implemented
Capture key performance metrics
Track customer Cases
Effective communication with GSC is a key to success

1-4 Copyright Oracle Corporation, 2004. All rights reserved.

 Scorecard

Scorecard template available at .....

Use as a template and adjust to suite the specific
engagement
To be used as a communication vehicle with
customer
Lets review the key aspects of the Scorecard

1-5 Copyright Oracle Corporation, 2004. All rights reserved.

 Scorecard - transactions

Identify key transactions

Detail steps to invoke transactions - navigation
Identify Performance success criteria response
times
Know when youre done
User
Navigation volume
Transaction
Description Goal

1-6 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance Monitoring

Progress must be based against measurable data

Performance metrics a vital aspect of any tuning
effort
Many different aspects of application need to be
monitored
End user response times
OS resource utilization at various layers
Tier specific measurements for Web, App, and DB tiers
Detailed in other seminars / vendor materials

1-7 Copyright Oracle Corporation, 2004. All rights reserved.

 Configuration Data Gathering

Web Server version

Including Service Packs and patches
JVM Version
Information available in Web logs
Jolt Rolling Patch level
Patchlev file in BEA install directory
App Server version
Lowest level of detail 8.45.08 not just 8.45
Database version
Lowest level of detail Oracle 9.2.0.6 not just 9.2
3rd Party software Verity, etc.
Record in Scorecard / include in GSC cases
1-8 Copyright Oracle Corporation, 2004. All rights reserved.
 Performance Monitoring - Tiers

End User response time

Interface throughput
Web Server
Application Server
RDBMS
Different metrics are important at each tier

1-9 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance Monitoring End User

Many tools available to measure response time

LoadRunner (Mercury)
MS Web Stress Testing Tool (free)
Stop watch (least reliable)
Seque
Psappsrv logging
Avoid user impressions, rely upon data
Important to establish data capture early in project
Capture data into Scorecard

1-10 Copyright Oracle Corporation, 2004. All rights reserved.

 Scorecard Response Times

Page to capture response times over time

Key measure of progress against established goals

Dates
Transaction

1-11 Copyright Oracle Corporation, 2004. All rights reserved.

 Response Times Graph

Graph derived from previous page

Can be more effective than text / raw data

Reduced Transactions
response
times

Date

1-12 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance Monitoring - Web

OS resources at Web tier

CPU Utilization
Memory consumption
Web server specific metrics
Differ by Web Server product
JVM garbage collection data often most critical

1-13 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance Monitoring App Server

OS Resources at app server layer

CPU utilization often most critical at this tier
Memory utilization
Tuxedo queuing often a critical measurement
PSFT product logs also important source of data
Psappsrv
Integration Broker processes
Process Scheduler

1-14 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance Monitoring - Database

OS Resources at database layer

CPU Utilization
Memory Utilization
Disk waits / IO rates
RDBMS specific metrics
Locking Get
Memory usage specialized
help!
Cache hit rates
Physical IO
Each RDBMS has specific metrics, monitoring

1-15 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance Monitoring - Network

Network monitoring often most difficult to capture

Relies on capturing information from all layers
Requires highest level of access to get detailed data
Least common source of performance problem
When it is a problem, problems can be pronounced
Metrics tend to be hardware / platform specific
Use simple metrics to get general info
Ping, ftp, or PSPING to get basic data
Pursue details only if warranted

1-16 Copyright Oracle Corporation, 2004. All rights reserved.

 System Statistics - Scorecard

Capture Performance metrics into scorecard

Establish baseline before changes
Measure affect of changes

1-17 Copyright Oracle Corporation, 2004. All rights reserved.

 System Statistics Graph

Present graphically to show improvement over time

Be careful not to include too many elements
Use secondary axis to mix different scales
Consider separate graphs for each tier or type
Metric

Use
secondary
Axis
Date

1-18 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance data - Scorecard

Use performance data / Scorecard as

communication vehicle
Quantitative
Unambiguous
Share with customer
Results will not always be as expected
Progress will not always be as quick as hoped
Benefits can be clearly articulated
Integrate into routine status meetings with customer

1-19 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance Testing

An integral part of Performance Tuning is

Performance Testing
AKA Stress Testing / Benchmarking
Key points
Realistic mix of work / transactions
Realistic transaction pacing
Include batch / messaging
Tests must be repeatable
Capture metrics for each run
Track changes made between tests

1-20 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance Data App server logs

One important source of performance data is

psappsrv logs
Log Fence = 4 records duration of key services
Can also provide actual measurement of mix of
work in Production environment

1-21 Copyright Oracle Corporation, 2004. All rights reserved.

 Problem identification / resolution

A key technique in identifying performance

problems is the SQL Trace
Can be generated through PIA (&trace=Y)
Can be done for the entire domain (high overhead)
Trace can be analyzed through PS Trace Viewer
Useful to identify SQL and PeopleCode performance
issues
Can identify many performance problems
Covered in separate seminar

1-22 Copyright Oracle Corporation, 2004. All rights reserved.

 PS Trace Viewer Sample 1

Shows tree
structure
of code Shows
durations

Shows
SQL
Trace

1-23 Copyright Oracle Corporation, 2004. All rights reserved.

 PS Trace Viewer Sample 2
Many
different
views

Organizes
SQL

Most
Expensive

1-24 Copyright Oracle Corporation, 2004. All rights reserved.

 Recommendations

Capture recommendations in Scorecard

Capture information requests in Scorecard
Monitor customer response to requests
Review with customer regularly
Content of recommendation
Timeliness of implementation
Impact of change use performance metrics

Reco Date Made

1-25 Copyright Oracle Corporation, 2004. All rights reserved.

 Involve GSC

A key to successful implementations is to engage

appropriate Support services
Educate customer on Support processes
Open GSC cases where appropriate
Educate customer on CRM and Tools GSC
When to open a case with which GSC
Track cases and next steps
Close cases when appropriate

1-26 Copyright Oracle Corporation, 2004. All rights reserved.

 Track Cases

Track cases and status in Scorecard spreadsheet

Review with customer and GSC regularly
Effective follow-through will result in effective
handling of cases speeds resolution

1-27 Copyright Oracle Corporation, 2004. All rights reserved.

 Performance Tuning Iterate / Review

Establish metrics collection

Prepare to perform Stress testing where possible
Gather application information / traces
Make / track recommendations
Gather impact data
Assess metrics against goals
Repeat until done
Solicit help from GSC where appropriate
Always more to learn, more tools, more techniques

1-28 Copyright Oracle Corporation, 2004. All rights reserved.

 For More Information
Performance Tuning Tools Seminar
PS TraceViewer Seminar
PS LogReader Seminar
Solutions from Customer Connection:
Solution-200991712 -How to Generate and Read traces
for PeopleSoft Applications
Solution-200746517-Resolving performance issues by
using Lookup Exclusion Table
Solution-200768681-Known Issues When Installing
CRM 88SP1MP1 or Tools 844

1-29 Copyright Oracle Corporation, 2004. All rights reserved.

 Thank You.

Copyright Oracle Corporation, 2004. All rights reserved.