Performance Improvement Plan

(PIP)

System P10
Objectives
• Performance measures for response time
• Review existing performance
• Discuss options for performance improvement
• Pros and cons of PIP options
Performance Measures for Response
Time
• Wait Time < 10% of total response time (<50ms)
• Roll In/Out < 20ms
• Roll Wait time < 200ms
• Load and Generate < 50ms
• Processing time < 2 * CPU
• Enqueue time < 5ms
• DB Time < 40% (Response time – Wait time)
• GUI time < 200ms

Source
Review existing performance
• Data taken for review is of Dec-2017, Nov-2017 and Oct -2017

Ø = Average
Scenarios for performance improvement
1. SAP Application parameters tuning
2. DB parameters tuning
3. DB Table reorganization and re-indexing

Ø = Average

4. Tuning expensive SQL causing high load

5. Tuning ABAP programs causing high load
6. Data Archiving
SAP Application parameters tuning
• Zero Administration Memory Management (ZAMM) is
recommended by SAP in note 386605.
• The memory configuration of the instance can only occur
using the PHYS_MEMSIZE parameter so we need to remove
other memory related parameters as those are calculated by
SAP Kernel.
• ZAMM uses physical memory (parameter PHYS_MEMSIZE),
that is the server's RAM, as a basis for calculating the other
memory parameters.
DB parameters tuning
• Follow SAP note 1431798 - Oracle 11.2.0: Database Parameter
Settings.
• List all parameters which are not set as per SAP note 1431798
recommendations.
• Modify / create parameters as per SAP recommendation.
• Should be done Dev and QA systems first and after
performance observation, can be set in Production system.
 DB Table reorganization and re-indexing
Below tables require reorganization and re-indexing.

Top 15 Heavy Tables Top 20 Fastest Growing Tables

Name Type Tablespace Size (MB) Name Type Tablespace Size (MB) Chg.Size/Month (MB)
SYS_LOB0000173706C00007$$ LOBSEGMENT PSAPDAT 369,366.00 7,076.88
SYS_LOB0000173706C00007$$ LOBSEGMENT PSAPDAT 372,445.00
SWWCNTP0 TABLE PSAPDAT 74,292.00 2,100.90
BALDAT TABLE PSAPDAT 111,860.00 GLPCA TABLE PSAPDAT 85,617.00 921.205
GLPCA TABLE PSAPDAT 86,037.00 SYS_LOB0000009882C00006$$ LOBSEGMENT PSAPDAT 45,509.00 847.151
COEP TABLE PSAPDAT 39,012.00 423.288
SWWCNTP0 TABLE PSAPDAT 75,335.00
LTEX TABLE PSAPDAT 23,230.00 382.767
CDCLS TABLE PSAPDAT 56,040.00 SWFREVTLOG TABLE PSAPDAT 32,402.00 361.808
DBTABLOG TABLE PSAPDAT 53,731.00 CDCLS TABLE PSAPDAT 55,784.00 360.74
SYS_LOB0000009882C00006$$ LOBSEGMENT PSAPDAT 45,509.00 BALDAT TABLE PSAPDAT 111,860.00 357.699
RFBLG TABLE PSAPDAT 27,912.00 301.397
SYS_LOB0000173694C00014$$ LOBSEGMENT PSAPDAT 44,715.00 ACCTIT TABLE PSAPDAT 25,637.00 297.123
COEP TABLE PSAPDAT 39,204.00 JCDS TABLE PSAPDAT 21,793.00 259.808
QCMBSEG TABLE PSAPDAT 37,843.00 MC18I00NTFSETUP TABLE PSAPDAT 3,110.00 255.616
SWWLOGHIST TABLE PSAPDAT 8,864.00 253.808
SWFREVTLOG TABLE PSAPDAT 32,530.00 BSIS TABLE PSAPDAT 23,182.00 247.315
EDI40 TABLE PSAPDAT 31,679.00 CE1SWT1 TABLE PSAPDAT 25,008.00 246.411
RFBLG TABLE PSAPDAT 28,040.00 JCDS~0 INDEX PSAPDAT 18,503.31 229.151
/WECO/W_USRCLP TABLE PSAPDAT 5,183.00 220.849
ACCTIT TABLE PSAPDAT 25,765.00 COEP~1 INDEX PSAPDAT 18,451.69 209.26
CE1SWT1 TABLE PSAPDAT 25,072.00 CE4SWT1_ACCT TABLE PSAPDAT 19,251.00 205.644
ABAP Tuning
• go to ST04 t-code --> performance --> SQL Statement Analysis --> Shared Cursor
Cache. Sort by SQL Statements by Total Execution Time(ms). Fine tune top
expensive SQL’s identified as per SAP note 551646.
• Fine tune below heavy custom programs from Dec-2017 data.
Program Average of Ø Time Average of Ø DB Time Average of Ø CPU Time
ZAWAFKOI_SWT_S21 18488325.62 9441679.154 416168.8462
ZWAAFVCIH_SWT 15063311.07 8269448.296 229283.7037
ZAWMARDI 13856958.28 12692032.92 1799592.8
ZAWSTPPMD 9737331.346 9382640.692 666236.5385
ZWNETWOPRATN_SWT 9493784.577 8482967.923 1698776.538
ZWBKPFBSEGD 8082076.6 5990180.2 2166080
ZAWBSEGCLEAR 7077780 5530303 1622716
ZTAX_ACCRUAL 6530762 2216128 11350
ZAWFPLT 5786952.4 5487382.218 373989.6364
ZAWSOCOMMD 5174651.462 4611178.077 587238.0769
ZWCCAEXTESSBASE 5131825.615 5108703.077 27230.38462
ZWCCAINTESSBASE 4394331.667 4352678.37 50141.11111
ZAWVP1SA 4167434.962 2350057.077 123.0769231
ZAWBUDCOSSSTG 3680022.2 2266516.967 2130693
ZAWBUDCOSPSTG 3529712.933 2264368.6 1991787.667
Pros.
1. Table reorganization enhances the DB performance
2. Re-creating indexes provides faster execution of reports
3. Z-programs optimization will lead to less consumption of
application and DB resources resulting in performance
improvement
4. Archiving of heavy tables will release database space
5. Archiving will help to reduce table and index size which leads
to enhanced DB response time
Cons.
1. DB reorganization may cause response overhead while
execution
2. Archiving will cause slower execution of reports while
reading from archives
3. Archives need to be backed-up separately
4. Archived data can be viewed using some specific tcodes
5. Custom programs may need modification if required to read
from archives
Thank You