Monday Feb 27, 2012

Demantra T_UPDATE Performance Issues? Supply an Enhanced AWR Report Using Logger

When communicating with Support or Development the performance issue you are experiencing with the T_UPDATE object, follow the instructions below to produce an AWR report with logger turned on. This may expedite your solution.

Please do the following:

1. Turn on the Logger Category 'appserver.update.sql' via server admin page.
    For example: http://<server>:8080/demantra/admin and then press the Logger Manager link.

2. Launch the AWR Report. See note 1279115.1, Producing an AWR Report for Demantra Performance Troubleshooting

3. Re-run the problematic scenario.

4. Turn off the Logger Category from step 1.

5. Supply the AWR report for the time period matching the Logger Category switch.

6. Supply the tables whose name starts with "T_UPDATE_". If they are very big then please list the T_UPDATE_  table names and their row counts.

Performance and RDBMS Tuning and Maintenance

Demantra is a Data Base resource intensive application.

- Evident from large implementations
- Large-scale implementations are global solutions across multiple regions or
  retailer oriented store-level solutions - Require very large demand data
  repositories storing billions of data points.

Common Demantra Performance issues
- Poor worksheet response times
- Longer Batch Engine run times
- Extended Simulation runs
- Prolonged Data loads
- Slow running user updates

These issues can be addressed by appropriate DB setup and tuning activities

Example 1.
This customer has been live on a Demantra VMI implementation and suddenly reported worksheet performance issues.

Sales_Data was ~32M records, non-partitioned

Highlights:
Analyze_Schema was not being run
Did a chained row count after Analyze_Schema – 48%
Recommended Rebuild_schema and worksheet performance improved 60% on average

 

Example 2.
This is a Demantra DM/PTP/DSM implementation. Just before UAT customer loaded full volume of Sales history,
Promotion and Settlement data and started experiencing serious worksheet performance issues.

MDP_Matrix=1.5M; Sales_Data=30M; Promotion_Data = 22M;

Highlights:
- CBO parameter changes
- Relocating null and empty columns in very large tables at the end of the row
- Sales_Data partitioning
- Reorder of Data by PK
- Worksheet specific Indexes

Performance Improvements reported:

Series Config Changes, 21%

GL Data Trim, 8%

Indexes, 2%

Reorder Data by PK, 32%

Worksheet Cache Refresh, 73%

Demantra Performance and Install/Upgrade Questions

Hello!  We are reworking this blog to specifically focus on Demantra performance and install/upgrade issues.   When reviewing you will find articles, such as the following, added on a frequent basis.   Questions are welcome.   Regards!   Jeff
About

This blog delivers the latest information regarding performance and install/upgrade. Comments welcome

Search

Archives
« February 2012 »
SunMonTueWedThuFriSat
   
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
28
29
   
       
Today