{"id":1052,"date":"2021-07-01T08:52:39","date_gmt":"2021-07-01T06:52:39","guid":{"rendered":"https:\/\/ad-astra.com.pl\/?p=1052"},"modified":"2021-07-01T08:52:40","modified_gmt":"2021-07-01T06:52:40","slug":"sap-analytics-cloud-performance-analysis-tool","status":"publish","type":"post","link":"https:\/\/ad-astra.com.pl\/en\/2021\/07\/01\/sap-analytics-cloud-performance-analysis-tool\/","title":{"rendered":"SAP Analytics Cloud Performance Analysis Tool"},"content":{"rendered":"

Perfomance Analysis Tool <\/strong>is a tool for viewing performance statistics that SAC automatically collects and stores in SAP Hana internal views. This tool is available with update 2021.02 and 2021.Q1 QRC, by default in the system folder directory in the SAC Content folder.<\/p>\n\n\n\n

The statistics content of the SAC consists of the following analytical models:<\/p>\n\n\n\n

– SAC_STATISTICS_MDS_QUERY_PERF<\/strong> (backend statistics)<\/p>\n\n\n\n

– SAC_USER_FRIENDLY_PERF_ACTION (<\/strong>(frontend statistics)<\/p>\n\n\n\n

– SAC_PERFORMANCE_E2E<\/strong> (network statistics as well as performance for a single user)<\/p>\n\n\n\n

Their purpose is to provide visibility into information related to the backend, network and user interface.<\/p>\n\n\n\n

Perfomance Analysis Tool<\/strong>  is based on the SAC_PERFORMANCE_E2E analytical model - in this case, the aforementioned content helps with the analysis of individual runs of reports or analytical applications<\/p>\n\n\n\n

How to use SAC Perfomance Analysis Tool?<\/strong><\/p>\n\n\n\n

 The tool can be run from the system folders directory, SAC Content folder.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The tool can be run from the system folders directory, SAC Content folder.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Ekran startowy PAT<\/strong> it consists of a search bar that allows you to narrow down the area on which you want to display statistics. The available options allow you to:<\/p>\n\n\n\n

- Setting the filter to date (the current day is selected by default)<\/p>\n\n\n\n

- Optional refinement of the search by selecting specific users and resources.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

To confirm the criteria press Search<\/strong> . A list of individual resource launches will appear. By clicking on the entry that interests us, we will go to the analytical part of the tool, which allows you to review the selected report or application.<\/p>\n\n\n\n

At the top of the interface there is a button that allows you to return to the start screen, where we can restart the analysis or change the filtering criteria. The button in the upper right corner of the page allows you to change the displayed analysis format (seconds or milliseconds)<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Overview section:<\/strong><\/p>\n\n\n\n

Below, divided into five columns, is an Overview <\/strong>(Some of the visualizations can be used to filter the tables and charts on this page.).<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The first column consists of information about the user and the selected resource.<\/strong> This information includes: Username, Timestamp, Report or Application Name, and Session ID. Note that the combination of resource ID and session ID is unique. It is also possible to open the asset under test directly from the tool which can be helpful in understanding the design, structure and complexity.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Next to this section, you can find information about individual pages<\/strong>that were part of the analyzed workflow. For each used page, we see the launch time - this is the time from the start of the action (e.g. opening a report or going to a specific page) to the full rendering of the last object on the page. Hovering the cursor over the graph elements shows the start time and name of the event. If a page has been visited twice, the chart will also show twice, as well as Page 1 and Page 3 in the example.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The third column is a graph of the top 5 widgets in terms of execution time<\/strong>. The times displayed are the sum of a single widget execution time. If the widget has been loaded more than once (e.g. the report has been opened many times or the filter criteria have been changed), each such loading is additionally added to this sum.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Fourth column is a chart with all the models that were actively used when the resource was started<\/strong> and their maximum operating time in the backend system. Only their single maximum value is shown here. Hovering the mouse over the graph will show the connection used by the model.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

The last section in the header is a distribution of the runtime among processing layers<\/strong>. This section contains two widgets that allow you to compare the maximum times per processing layer with the median of the corresponding layer.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Each of these widgets has an information icon - clicking on it will display a brief explanation of the widget and the indicators used.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Below the Overview section are three tables -  Runtime Distribution, Page Load Time <\/strong>and Widget Drilldown.<\/strong><\/p>\n\n\n\n

Runtime Distribution<\/strong>  zawiera czas rozpocz\u0119cia akcji, jej nazw\u0119 oraz numer strony. Wska\u017anik przedstawiony na  wykresie to ca\u0142kowity czas dzia\u0142ania, stanowi\u0105cy zagregowan\u0105 warto\u015b\u0107 wszystkich wid\u017cet\u00f3w uruchomionych przez akcj\u0119.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Page load time<\/strong> structure similar to the previous chart, but with different indicators and no aggregation. The total time per action is shown - from the moment of its initiation to the rendering of the last widget on the page. This value can be divided into Page Preparation and Widget Load Time. To preview the complexity of an object, the number of widgets per action or page is also shown.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Page Preparation<\/strong> is the time from the start of the action to the start of loading the first widget.<\/p>\n\n\n\n

Widget Load Time<\/strong> is the time from the beginning of the first widget to the end of rendering of the last widget.<\/p>\n\n\n\n

The sume of those elements is a total time of an action.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The last columns of this view are the maximum values for each processing layer.<\/p>\n\n\n\n

Looking at the examples, we can see that for Open Story on page 1, one of the 17 widgets took 2.78s in the backend system, the same or another widget took 0.29s in the network and the same or another widget took 2.31s in the frontend system.<\/p>\n\n\n\n

At first glance, this structure may seem not very detailed, but thanks to it, we can directly detect actions that had no interaction with the backend system and were processed only in SAP Analytics Cloud.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Widget drilldown<\/strong> allows you to implement data down to the level of a single widget per action, model or page. Especially useful in this area is the filter bar above the tabs - it shows the current state of the filter, which applies to all views and charts below.<\/p>\n\n\n\n

Filters can be set by clicking on the graph elements of interest in one of the three mentioned tabs or in the Overview section. The bar also allows you to remove existing filters. In the example, the filter was set to Page 1 and the action \"Open story\".<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

We now get a complete list of all the widgets that were rendered on page 1 for Open Story, information like name, type, and end-to-end time for each widget.<\/p>\n\n\n\n

To get more details, we can go to Widget Details. <\/strong>For this purpose, we mark a specific position in the Widget Drilldown <\/strong>. This causes an additional filter to be set and detailed data to be displayed.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Widget Details<\/strong> contain information about the model used by the selected widget, the connection used by the model, runtime distribution, and display full requests to the backend.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The last part of the Performance Analysis Tool consists of Time-Series Charts<\/strong>. They allow you to compare the execution times for a single user against all SAC users, both at the page and widget level (the filtering mechanism works the same as in the previous items).<\/p>\n\n\n\n

In this section, the visualizations are divided into two groups - the charts on the left focus on the median execution times, while the charts on the right show the distribution of the execution times per layer.<\/p>\n\n\n\n

When you apply a filter at the widget level, the measures and chart titles will change - Median of Total Time<\/strong> and Total Time per Date<\/strong> will be changed to Widget Time per Date<\/strong> and Median Widget Time<\/strong><\/p>\n\n\n\n

Total Time per Date<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Widget Time per Date<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The chart group on the right has the same logic. When a filter is applied at the widget level, they update to reflect the distribution of runtime for a single widget. The titles and indicators do not change.<\/p>\n\n\n\n

Breakdown of Execution Time by Date - Action Level<\/strong><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Breakdown of Execution Time by Date - Widget Level<\/strong><\/p>\n\n\n\n

\"\"<\/figure>","protected":false},"excerpt":{"rendered":"

Perfomance Analysis is a tool for viewing performance statistics that SAC automatically collects and stores in SAP Han's internal views. This tool is available with update 2021.02 and 2021.Q1 QRC, by default in the system folder directory in the SAC Content folder.<\/p>","protected":false},"author":2,"featured_media":1102,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[7],"tags":[89,20,21,91,90],"_links":{"self":[{"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/posts\/1052"}],"collection":[{"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/comments?post=1052"}],"version-history":[{"count":9,"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/posts\/1052\/revisions"}],"predecessor-version":[{"id":1104,"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/posts\/1052\/revisions\/1104"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/media\/1102"}],"wp:attachment":[{"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/media?parent=1052"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/categories?post=1052"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ad-astra.com.pl\/en\/wp-json\/wp\/v2\/tags?post=1052"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}