SAP Analytics Cloud New Optimized Story Performance Deep Dive and Recommendations

[jove_shi]

SAP Analytics Cloud new optimized story offers new cache mechanisms to improve the overall initial loading performance, plus new settings to allow story developers to adjust the widgets loading sequence to achieve best performance for different scenarios. The learning journey "Managing Performance in SAP Analytics Cloud" (based on 2024.15 release) has been released to provide you with the knowledge and skills required to be able to successfully manage performance in SAP Analytics Cloud. You will gain insight into SAP Analytics Cloud performance tools and troubleshooting performance issues in SAP Analytics Cloud stories.

Check out the learning journey: https://learning.sap.com/learning-journeys/managing-performance-in-sap-analytics-cloud

The original content of this article has been merged and updated as "Optimizing Performance in Data Loading" chapter of the learning journey: https://learning.sap.com/learning-journeys/managing-performance-in-sap-analytics-cloud/exploring-dat... 

[word_expert]

Well, First of all, it is really interesting topic and the segment about bookmark, was the best part. But can you little explain your point which you mentioned,

• When the story is re-saved, the cache will be invalid. Then a user first time views the story, a public cache will be re-generated and associated with the story and bookmark.

If the cache will be re-saved for the first time user, then it will create extra burden on server. What are your thought about this factor?

[jove_shi]

Hi Tufail,

When the story is re-saved, its bookmark's related cache will be re-generated only once when the first end user opens the bookmark. Not for every end user, so the extra overhead on the server is quite small.

Thanks,
Jove

[JefB]

The cache will be useless for widgets which queries are modified by story page – onInitialization event script, e.g. Chart.getDataSource().setDimensionFilter(dimension, members).

Hi jove.shi

Is the widget query cache retained when setting a (story wide) filter on the FileDataSource object, or story dim or variable in URL filter, or any other best practices to filter data and keep the widget query cache for fast story loading?

[yoavyahav2]

Hi jove.shi

 

regarding this statement in your blog:

 

"When the story created by new optimized design experience is saved..."

 

Will public cache rules be applied to SAC stories which are just converted to OVM?

 

Regards

 

Yoav

[jove_shi]

Hi Jef,

When the widget query is changed by story page – onInitialization event script or URL parameter, it requires re-loading required metadata and re-building its query instead of retrieving from cache. If your initial loading query scenario is limited, you can also try creating a bookmark which also supports caching widget's modified state.

We are continuously improving the loading performance like enhancing such cache mechanism to support more scenarios.

Thanks,
Jove

[jove_shi]

Hi Yoav,

OVM also supports such cache.

Thanks,
Jove

[JefB]

Hi Jove,

We seem to have an issue when URL parameters are passed to filter the data.
In our usecase, sometimes an URL filter (BW Model variable) is provided, but sometimes not. In this case we see sometimes the filter is not applied.

Is there a way to disable the query cache?

[jove_shi]

Hi Jef,

You can re-save the model, or change one of the dimension description then change back and save the model. Without re-saving the story, the query cache will be invalid and re-generated for per user's first time view the story.

If you can pre-produce the URL parameters (filter, variable) is applied randomly, please log a ticket that our dev team can take a look.

Thanks,
Jove