Best Practices for Performance Optimization in Your Story Design
These tips will help you discover ways to optimize the performance of your SAP Analytics Cloud story.
You want your SAP Analytics Cloud story to run smoothly, to have the best performance. The following tips will help optimize your story's performance.
Select a link to go directly to a tip.
Use Fewer Pages
When your story has a lot of pages, adding another page could decrease the story's performance.
For faster performance, you can create a new story or rearrange the story's content to use fewer pages.
If you are planning to rearrange the content, try to limit the number of data-related (process-heavy) widgets on a page.
Manage the Number of Process-Heavy Widgets on a Page
Story performance can be impacted when your story has a lot of widgets on a page, particularly data-related (process-heavy) widgets. For example, you have several charts, tables, or filters on a page. Processing data from those widgets can slow down the story's performance.
To determine the best performance for a story, the widgets are assigned a unit weight, with the maximum ideal weight per page set to 5 units.
The following table shows the unit weight per widget.
| Widget | Unit Weight |
|---|---|
|
Table |
0.6 |
|
Chart |
0.3 |
|
Geo map |
1 |
|
Filters, expanded |
0.4 |
|
Filters, non-expanded |
0.2 |
|
Section on page |
0.5 |
|
Value Driver Tree |
1 |
|
R Widget (with at least 1 data frame) |
1.2 |
|
Text box with dynamic text |
0.2 |
|
Dynamic Image |
0.3 |
|
Commenting widget |
0.1 |
|
Text box |
0.1 |
|
Iframe/ web page |
0.1 |
|
Rss feed |
0.1 |
|
Image/shape/clock |
0.1 |
If you have a page that contains the following widgets, you will be close to the maximum weight and may start to see performance issues.
| Widgets | Weight | Total Weight |
|---|---|---|
| 2 Geo maps | 1 | 2 |
| 4 charts | 0.3 | 1.2 |
| 2 tables | 0.6 | 1.2 |
| Expanded filter | 0.4 | 0.4 |
| Grand total | 4.8 |
For faster performance, consider changing the types of widgets that you are using or reducing the number of heavy widgets per page.
Collapse Page Filters and Input Controls
Expanded page filters or input controls are convenient because you can quickly select members or search for members in the control. However, an expanded input control refreshes often and that can affect the story's performance.
When the input control is collapsed, you must select the control to display the member list before you can search or make your selections.
When you have a high cardinality dimension (a dimension that has 100 dimension members or more), leaving that dimension expanded can affect your story's performance.
Input controls for hierarchy dimensions can also affect the story's performance when expanded, even if they have fewer members.
Manually Set Top N
If you have high cardinality dimensions, consider manually setting the Top N values rather than using Auto Top N.
When Auto Top-N is used, all the data is transferred from the system before the Top N data is rendered. When you use Top N, the data is sorted and the Top N values are selected in the system. Only the Top N data is sent.
Keep Images Small
Whenever possible, upload background images that are 1Mb or smaller. Larger images take longer to load and will have an impact on your story's performance.
To get a good quality background image, you could use a compressed web image or you might want to use an SVG image.