Performance Best Practices for Analytics Designer Webcast Recap

[TammyPowlas]

 

Source: SAP

jie.deng  is the SAP product manager/speaker/presenter

Bob is a development architect for the Analytics Design team

Thanks to ingo.hilgefort for setting this up; thanks to Jie and Bob for a great webcast

Overview

Source: SAP

Analytic Designer – create analytical application

It is fully integrated in SAC

It is a low code development environment within SAC

Scripting, eventing, widgets, more for enterprise applications or dashboards

Source: SAP

Use script capabilities to do customizing work

Integrate into 3rd party app

Custom widgets to create own visualizations

Future – composite and template capabilities to reuse code/widgets

Product scope is wider than Lumira Designer

Integration with planning, closed loop scenarios

Review Developer Handbook and API documentation

Developer Handbook: https://www.sapanalytics.cloud/analytics-designer-handbook/
API Reference Documentation: https://help.sap.com/doc/958d4c11261f42e992e8d01a4c0dde25/latest/en-US/index.html

Source: SAP

Mid May, Q2 QRC release

1.Mobile support

2.Scheduling, publications

3.Integration with Data Warehouse Cloud

4.Copy widgets – reuse story artifacts to Analytical Application

5.Different API enhancements, different interactive scenarios

6.Odata enhancements

Source: SAP

Source: SAP

Technical background to understand foundation

High level architecture diagram

SAC shell at top – SAC UI – menu bar, etc

It has the application container

Widgets are managed by the story container

Data access is managed by individual widgets

Best Practices

Best practices of story are valid for analytic applications as well for those widgets that are shared between these 2 artifacts (table, chart, geo map etc.).  For details please refer to the best practices of story: https://www.sapanalytics.cloud/resources-performance-best-practices/  (Source: SAP)

Source: SAP

Browser – best using Chrome

Cache definition of story in browser; only possible in Chrome

Avoid building complex applications in one document

Numeric point charts; consider getData API; check whether it applies to your scenario

Mobile – reduce number of charts, time series

Look at memory recommendations

Use embed mode; without shell around – don’t see toolbar, just see content

Source: SAP

Try to reduce data that is downloaded

For charts, lower the number of data points

Table – limit to rows/columns needed for initial view

Geo maps – to on location clustering

Images – size should not be big; not bigger than MB

Reduce number of widgets; use Move API – move widget to a different container

Source: SAP

Setvariable value in BW live connections

-Variables are different than HANA, different round trips

-Call in a row so 1 backend call

Prefer filter over variable value to avoid additional round trips

getMembers reads all master data; use getResultset API so you can retrieve data already downloaded to avoid round trips

Startup behavior  - one, on initialization event is called when all widgets are loading; if change filter/variable on a widget in startup it triggers another round trip; try to avoid such calls.

Avoid repetition in loops – a general best practice from development

Source: SAP

Loading behavior – seen recommendations

Minimize data sources at start up

New features – avoids loading invisible widgets – see above – once you do this, invisible widgets will load in background

Coming in Q3 release

Source: SAP

Left is the default behavior

Right hand side, turn on invisible widget in background, only visible widgets initialize

Right columns shows best practices

Source: SAP

Planning in performance

Q3 – load invisible widgets in background

Q4 – further improve invisible widgets load – entry for listbox – can manually configure

Future – more configuration options for invisible widget load in background

Ways to measure performance

Road map is subject to change