Discussing Performance

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Identify performance aids and guidelines

Performance Aids

Follow the steps in the following decision tree to find resources that will help you to resolve performance issues (if necessary).

As an administrator of an SAP Analytics Cloud tenant, you can use the Performance Analysis Tool and the decision tree below to find resources that will help you resolve performance issues.

Use this link to access the on-line decision tree: https://help.sap.com/doc/DRAFT/00f68c2e08b941f081002fd3691d86a7/2022.10/en-US/6ae71d6ad2eb4622b0ef9feef61efba4.html#concept_jwn_jpp_dtb__section_stories

The performance content is included in the Files → Systems folder (and accessible by administrators) for customers. In the training landscape, the SAC Content folder has been shared with the A and B Teams.

Customers can use the built-in performance content to manage system performance.

It will be deployed per default into your system folder directory into the SAC Content folder. You don‘t need to deploy it from the Analytics Content Network. Everything will be available out of the box for your convenience.

The analytic models, stories and analytic applications are provided off-the-shelf. For more information, follow this link: https://blogs.sap.com/2021/01/08/sap-analytics-cloud-performance-analysis-tool/


SAP Analytics Cloud enables you to perform sophisticated analysis on large volumes of intricate data. These complex scenarios can sometimes lead to less than ideal performance times for end-users. However, there are things you can do when designing models and stories that will help SAP Analytics Cloud run at optimal performance levels.

Performance can be impacted by many factors from network speed, the number of widgets in a story, the number of data cells in a table just to name a few. Of course, the designers have their marching orders from the information consumers but they cannot ignore the possible performance impacts of their design decisions. In other words, it is a balancing act between the needs of the business users vs. performance. As designers go through the design phase, they need to do stress testing based on real-life data volumes if possible.

In the following section, we'll list a few guidelines. As usual there are no hard limits on the number of charts per story or data cells per table because there many factors at play. In other words, take these guidelines with a grain of salt.

  • In Model Preferences under Data and Performance, toggle on "Optimize Story Building Performance". This prevents the automatic refresh of data during story design.
  • Whenever possible, choose unbooked data. This means that the software has to spend less time differentiating between booked and unbooked data.
  • Avoid specifying Exception Aggregations in the Model and instead, use the restricted measures or calculation functionality or in your stories.
  • Try designing your story using Responsive pages instead of Canvas or Grid pages. Responsive pages allow your story content to re-flow depending on the size of the screen it is being viewed on.
  • Rather than designing a large story with many pages, try to limit your pages and create different stories for each use-case or audience. If you want to refer to a related story, you can add a hyperlink to a different page, story, or external website.
  • Use pages to break up your story by category or type of information. Put your most-viewed content on the first page to make it easily accessible.

  • When adding images to your pages ensure that the images are sized for web and are smaller than 1MB. SVG vectors image files still look great at a small file size. If you can’t use an SVG image file, PNG image files perform better than JPG.
  • To ensure performance when working with blended data, avoid creating linked dimensions on calculated dimensions. on . Keeping the number of models linked in each story at a minimum will also improve overall speed and performance.
  • Limit the number of content-rich tiles on each page like maps or charts with a high volume of data points. Overloading your pages with dense information will make it harder for your viewers to consume and may slow load-time.
  • Try to keep the number of individual tiles on each page of your story limited to six or less
  • Limit the number of widgets on a page. Note: multiple widgets per page are certainly allowed but an extremely high number of widgets in a page may affect the refresh time for a story.
  • Limit the number of charts on the page to enhance readability, decrease the number of back end requests, and improve performance
  • Avoid charts with more than 500 data points.
  • Apply chart filters to reduce the volume of information in charts with more than 1000+ data points and use table filters to keep a manageable amount of information visible in your tables.

  • For a Dimension with a large Hierarchy and an ALL node it is recommended to use the chart drill capability for best performance.
  • Be aware of progressive chart rendering, which enables chart widgets to display more quickly when a story is opened a subsequent time (within an hour). This setting is enabled by administrators.
  • For Tables with Large datasets, it is recommended to avoid Formatting Rules
  • Apply the Top N feature to charts and tables

  • Limit the number of tables on the page to enhance readability, decrease the number of back end requests, and improve performance

  • When adding tables to your story, keep in mind the goal of the table and ensure that viewers can easily navigate the information. To help ensure readability, try to limit your tables to a maximum of 500 rows and 60 columns. If you need to display more, you can edit the drill limitation. Keep in mind that the more cells you include, the harder SAP Analytics Cloud has to work to display them.
  • Enable the "High Performance" power plan (in your computer settings) if scrolling in tables is slow

Optimized View Mode

Viewport rendering is available for stories in classic design mode assuming all of the requirements are met. Viewport rendering is the default refresh behavior when using Optimized Design Mode.

Save progress to your learning plan by logging in or creating an account