PeopleSoft Connect 2003- Enterprise Reporting Session6451_final

7/31/2019 PeopleSoft Connect 2003- Enterprise Reporting Session6451_final

1/39

PeopleSoft Proprietary and Confidential, Copyright 2003 PeopleSoft, Inc.For Internal Use Only, Do not distribute outside of PeopleSoft.

Tuning PS/nVision for Optimal

Performance

Geoffrey Birungi Bazira

Tools: Enterprise Reporting

Session 6451

September, 17th 14:15 to 15:15


2/39

Page 2 PeopleSoft Proprietary and Confidential, Copyright 2003 PeopleSoft, Inc.For Internal Use Only, Do not distribute outside of PeopleSoft.

This Session Covers

PS/nVision process flow Where nVision spends its time

Where you can make a difference

Environment Layout

Indexing for performance

Tree performance options

Summary ledgers

Summary

Q and A


3/39


What Happens when I run an nVision report?

Labels

Amounts

Process

SchedulerServer

Start

ReportBook

ReportReqst

Scope

Layout

Start

Strings

Get

Criteria

Read

Metadata

Build

SQLResults

Open

Generate

Instance

Issue

Fetch

Create

Instance

InsertRows

Formatting

BulkCopy

Calcs

Inst.Hoo

ks

Instance


4/39


Where PS/nVision spends time

Labels

Amounts

Process

SchedulerServer

Start

ReportBook

ReportReqst

Scope

Layout

Start

Strings

Get

Criteria

Read

Metadata

Build

SQLResults

Open

Generate

Instance

Issue

Fetch

Deliver

InstanceInstance


5/39


Where PS/nVision may spend time (cont..)

PSNVS.EXE is started

Starting PeopleTools

Preloading cache

Establishing object authorization

Starting Microsoft Excel

PS/nVision Parsing Layout Criteria

Digesting Report Scope and Meta Data


6/39


Where PS/nVision may spend time (cont..)

PS/nVision issues all SQL statements Finding the data to be returned

Slow un-tuned SQL

Joins with Tree Criteria

Joins with Authorization Tables and Trees Aggregating data thats too granular

PS/nVision creates and populates instance

Inserting all data

Contention between concurrent processes

Performing Microsoft Excel formula calculations

InstanceHooks


7/39


Where you can make a difference

Environment tuning

Layout tips

Intelligent indexing


Summary ledger


8/39


Environment Tuning

Microsoft Excel Properly installed

Files and Macros in the XLStart Folder

Outlooks Journal Lines Entry Feature (Excel 97)

Database Server / Batch Server I/O - Disk Fragmentation Memory

CPU

Network

Network Load

Optimized NIC

Real-time Tracing or Logging


9/39


Layout Tips

Microsoft Excel version of your layout file

Distinguish Ad-Hoc Vs Batch type

Instancehook macros Selected Detail Values instead of Tree joins

Consider not formatting unused cells

Pivot Tables performance hogs Have a power user review all layouts


10/39


Indexing - overview

Indexes tell the database how to find yourdata

Sequence of fields is important

Determines how much work the database has todo to find a row

Indexes are expensive

Take up valuable disk space

Decrease Insert, Delete and Update performance


11/39


Indexing Simple Example

Assume following SQL

SELECT FISCAL_YEAR, PERIOD, ACCOUNT FROM LEDGER

WHERE FISCAL_YEAR = 2003 AND ACCOUNT = 50050

If table has data for 4 fiscal years and 800accounts:

Choosing Index on FISCAL_YEAR narrows search by 1/4

Choosing Index on ACCOUNT narrows search by 1/800th


12/39


Indexing - Goals

Minimize number of indexes by designing them tocover most SQL statements against that table

Sequence columns used most at beginning of index

Make indexes effective by picking columns that

segment the data table well Sequence effective columns at beginning of index

When picking fields to include in an index, balancethe following

Cardinality of column values

Sparsity (Density) of column values

Frequency column is used in WHERE clause

How column is used in WHERE clause


13/39


Indexing - PS/nVision Examples

Rule Example of poorchoice

Example of goodchoice

Cardinality of values FISCAL_YEAR ACCOUNT

Sparsity(or lack of sparsity)

BUSINESS_UNIT,PRODUCT

ACCOUNTING_PERIOD

Frequency of Use PRODUCT,PROJECT

ACCOUNT,BUSINESS_UNIT,FISCAL_YEAR,ACCOUNTING_PERIOD

How Used ACCOUNT, DEPTID BUSINESS_UNIT,FISCAL_YEAR


14/39


Indexing - Make the most of your optimizer

Optimizer - Brains of RDBMS Formulates SQL Execution Plan

Two kinds of optimizers

Cost based recommended approach for nVision

Rule based

Do you like what your optimizer is giving you?

Look at your SQL

Use SQL Trace Show Report SQL PS/nVision Option

Look at your optimizers Explain Plan


15/39


Indexing - Make the most of your optimizer (cont..)

Run Statistics

Poor statistics poor Execution Plan

State of tables at time statistics are calculated canhave a dramatic affect on performance

Seeding Tables is a way to affect statistics


16/39


Tree performance options - Overview

Labels

Amounts

Prcs

Schdlr

ReportBook

ReportReqst

Scope

Layout

Start

Get

Criteria

Read

Metadata

Build

SQLResults

Open

Generate

Instance

Exec

Fetch

Deliver

InstanceInstance

Build

SQL

TreeSelectors Join

Tree Objects

Build

Selectors


17/39


Tree performance options Default SQL Join

PSTREESELECTnn L

ACCTROLLUP TreePS_LEDGER

PSTREESELECTnn L2

DEPARTMENTS Tree


18/39


Tree Performance Options - Selector tables

EXP

EXPA

1000-1499

EXPB

2000-2199

Tree Selector Table (PSTREESELECTnn): Ledger Table:

Sel # Node # From To B. U. LEDGER ACCOU Amount123 1234567 1000 1499 M04 ACTUALS 1000 100.00

123 1234789 2000 2199 M04 ACTUALS

M04 ACTUALS 2001 100.00

991 1234789 2001 M04 ACTUALS 2001 100.00

991 1234789 2010 M04 ACTUALS 2010 100.00

991 1234789 2050 M04 ACTUALS 2090 100.00

991 1234789 2090 M04 ACTUALS 2090 100.00

991 1234789 2100 M04 ACTUALS 2090 100.00

991 1234789 2150 M04 ACTUALS 2150 100.00991 1234789 2180 M04 ACTUALS 2180 100.00

M04 ACTUALS 2180 100.00

M04 ACTUALS

Static Selector: join

using "BETWEEN"

or ">=


19/39


Tree Perf. Options Default SQL statement

SELECT A.ACCOUNT, A.DEPTID, SUM(A.POSTED_TOTAL_AMT)

FROM PS_LEDGER A, PSTREESELECT10 L, PSTREESELECT10 L1

WHERE A.LEDGER='LOCAL'

AND A.FISCAL_YEAR=1995

AND A.ACCOUNTING_PERIOD BETWEEN 1 AND 12

AND A.BUSINESS_UNIT='US001'

AND L.SELECTOR_NUM=215

AND A.ACCOUNT>= L.RANGE_FROM_10

AND A.ACCOUNT = L1.RANGE_FROM_10

AND A.DEPTID


20/39



Provide ability to tune SQL Tree criteria may cause time consuming joins

Customer controlled Settings for each tree

Defaults in Tree Manager

Overrides in PS/nVision layout

Permit fine tuning of production critical reports


21/39



Control Whether staging is done

Suppress Join

Control Persistence of Selectors

Static

Dynamic

Control How Selectors arePopulated

Single Values

Ranges

Control Syntax of Join for Ranges

Between

=


22/39


Tree performance options Access Method

Suppress join

Adds detail values/rangesto WHERE clause

Efficient for multiple treereports

Great with tree in scope

PSTREESELECTnn L1

PS_LEDGER

PSTREESELECTnn L

Literal Values


23/39


Tree Performance Options - Suppress Join


FROM PS_LEDGER A,PSTREESELECT10 L







AND A.ACCOUNT


24/39


Tree performance options - Tree Selectors

Static selectors - (default method)

Selector exists until tree changes

Dynamic selectors

Selector built for this report

Contains only required part of tree

Enables more streamlined join


25/39


Tree Perf. Options Dynamic Selector Example







AND L.SELECTOR_NUM=215AND A.ACCOUNT>= L.RANGE_FROM_10


AND A.DEPTID


26/39


Tree Perf. Options Dynamic Selector Options

Ranges of values

Control over join syntax

BETWEEN is best on most platforms

Single value selector

Usually most efficient: equi-join

Builds selector from detail table Can take longer to build selector

Ideal for multiple instances


27/39


Tree Performance Options - selector tables

EXP

EXPA

1000-1499

EXPB

2000-2199

Tree Selector Table (PSTREESELECTnn): Ledger Table:

Sel # Node # From To B. U. LEDGER ACCOU

Amount123 1234567 1000 1499 M04 ACTUALS 1000 100.00

123 1234789 2000 2199 M04 ACTUALS

M04 ACTUALS 2001 100.00

991 1234789 2001 M04 ACTUALS 2001 100.00

991 1234789 2010 M04 ACTUALS 2010 100.00

991 1234789 2050 M04 ACTUALS 2090 100.00

991 1234789 2090 M04 ACTUALS 2090 100.00

991 1234789 2100 M04 ACTUALS 2090 100.00

991 1234789 2150 M04 ACTUALS 2150 100.00

991 1234789 2180 M04 ACTUALS 2180 100.00

M04 ACTUALS 2180 100.00

M04 ACTUALS

Static Selector: join

using "BETWEEN"

or ">=


28/39


Example - Dynamic Selector with Single Valuesset on Departments Table









AND A.ACCOUNT


29/39


Tree Perf. Options Default SQL statement

DEFAULT:

SELECT A.ACCOUNT, A.DEPTID, SUM(A.POSTED_TOTAL_AMT)FROM PS_LEDGER A, PSTREESELECT10 L, PSTREESELECT10 L1








AND A.DEPTID = L.RANGE_FROM_10


AND A.CURRENCY_CD='USD'

AND A.STATISTICS_CODE=' '

GROUP BY A.ACCOUNT, A.DEPTID


30/39


Summary Ledgers

Reducing the overall ledger size based onChartField compression

Ledger

10 Million Rows

Summary Ledger

10 Thousand Rows


31/39


Summary Ledgers

Maximizing compression

Reduce number of ChartFields

Consider using a summary calendar to map

periods into quarters or even year-to-date

Roll up one or more ChartFields using trees - storenode names in Summary Ledger

Review PS/nVisions Translate features


32/39


Other Performance considerations

Deleting orphaned rows from Selectors Purging Tree Selectors (with caution)

Rebuild of Selectors when you modify size of aChartField

Number of Tree levels does not affect performance

Trade-off between elaborate security andperformance For example - Authorizations using a tree not encouraged

when accessing high volume data

Run subset of reports to pre-load cache Limit number of concurrent PS/nVision instances to 5

or 6 per batch server


33/39


Other Performance considerations (cont..)

SCODE errors Symptoms of MS Excel complaining e.g.

Invalid file name

Cant save because of permissions

Directory specified doesnt exist

Improperly designed macros

PS/nVision exits without completion

nVision may be trying to generate two reports concurrentlywith the same name use %RID%

PS/nVision stays in initiated state Check psprcs.cfg file to make sure instance directory is well

qualified Sometimes using UNC path is better


34/39


When should we tune?

Critical to consistently measure performanceof large reports or large batch jobs

Weigh the cost of reporting time Vs Size ofreports


35/39


Recommended Approach

Power User and DBA partnership tocoordinate

Review of layouts before they get to production

Reporting needs and Data distribution

Indexing

PS/nVision tree performance options

Running statistics

Find out what performance monitoring toolsyour RDBMS provides

Review the nVision Red Paper


36/39


Summary

nVision process flow

Where we spend time

Where we can make a difference

Tools to help us

Action plan


37/39


Whats new in PS/nVision 8.44

Extra logging capability that shows functionsexecuted

Can restart Report Requests andReportbooks

Can set time limits for PS/nVision processes

Microsoft Excel concurrency issuesminimized

Report books and Requests can be securedas Public or Private


38/39


Where to find more information

PeopleBooks

PS/nVision Red Paper

Customer Connection(www.peoplesoft.com)

PS/nVision performance tuning document

Global Support Center


39/39

Page 39 PeopleSoft Proprietary and Confidential Copyright 2003 PeopleSoft Inc

Questions?

Date post:	05-Apr-2018
Category:	Documents
Upload:	geoff-bazira
View:	219 times
Download:	0 times

PeopleSoft Connect 2003- Enterprise Reporting Session6451_final

Documents