Symptom
- SAP Analytics Cloud (SAC) is built based on SAP Datasphere (DS) Analytic Model and there is a performance issue
- In PlanViz Trace most of the time is consumed by TotalsMembers and Result Value Suppression
Environment
- SAP Datasphere
- SAP Analytics Cloud
Reproducing the Issue
- Executing the SAC Story
- Preview the DS Analytic Model
Cause
There are multiple reasons why performance might be affected. To break down the issue follow the below:
- To identify the reason of the performance issue we highly recommend go through our support content wiki.
- The PlanViz Trace will gives us the information where the most of the time is consumed. In this case the most of the time is consumed by TotalsMembers and Result Value Suppression.
- MDS query will show us how the story or analytic model is designed. The query shows us that the model is huge contains too many attributes.
- Enabling TotalMembers and Result Value Suppression will require some resources.
- The user can enable the features, but it is important to consider how many attributes are in the drill down.
Resolution
- Reduce the number of dimensions.
- Reduce the number of measures requested.
- Add more restrictive filters.
- Rather create multiple stories, then creating such a big SAC Story with all attributes or measures in the drill down.
If the Story is still designed costly, then try following recommendations:
- Consider to deactivate zero suppression as a higher data volume is transferred to the frontend application which may lead to performance.
- Consider to deactivate totals.
See Also
- Troubleshooting of Performance Issues Between SAP Analytics Cloud (SAC) and Datasphere
- KBA 3307074 - Guidelines for addressing SAP Datasphere issues within SAP Analytics Cloud
Keywords
sac, performance, totals, suppression, zero, null, analytic model , KBA , DS-MD-AM , Analytic Model , DS-MD , Modeling (Data Builder) , Problem
Product
SAP Analytics Cloud all versions ; SAP Datasphere all versions