Measuring the Performance of the Web Dynpro Framework 

Use

When the Web Dynpro framework processes a query, this query passes through various phases during the response-request cycle. Web Dynpro Console contains a table with information about how long [in msec] the individual phases of a query took to execute in the phase model in the Web Dynpro framework.

Prerequisites

       1.      You have administrator rights for Java Engine or for SAP NetWeaver Portal.

       2.      Web Dynpro Console has been launched.

More information: Web Dynpro Console

Procedure

       3.      In the tree menu, choose Admin Menu → Performance → Web Dynpro Framework and set the component package. In the standard setting, runtime package com.sap.tc.webdynpro.runtime* is set.

       4.      You can view the measurement data for both elapsed time and CPU time. The CPU consumption can be measured for both Windows and Linux platforms.

       5.      The measured times are accumulated with each call for the individual phases. If you want to sort the order of the values displayed, click once in the header of the column in question.

       6.      The results of the added times for each run are displayed in the GrossTotal column. The first line automatically displays the method that has consumed the greatest amount of time. In other words, the display is sorted in descending order.

Column GrossAvg displays the average time for a phase, that is the average value for n runs. This allows you to check, for example, how long method com.sap.tc.webdynpro.runtime.ClientManager.start (construct of class ClientManager) took on average and where in the phase model the times were primarily required by the Web Dynpro framework.

Gross times for a method are accumulated times including the times for subprograms and other methods. Net times are gross times minus the times for subprograms and other methods. This makes it possible to determine whether the method itself is the cause of the performance problem or whether the subprograms are behind it.

       7.      The NoCall column shows how often the call has been suppressed, and only the object has been returned.

       8.      You call up additional technical information about the component in question from the context menu.

Application: Information about the software component, development component, packages

View Element: Text elements, text resource

View Resources: Table overview of translatable texts

System Information: Provides information about Web Dynpro client capabilities, accessibility mode, server node ID, Java Virtual Machine, operating system

Extensions: Contains detailed technical information, for example about patterns

There is an option to store the information from the various tab pages locally in a text file.

       9.      By choosing the ClearTable option, you can delete table entries from the display; measurement data will not actually be lost, though.

   10.      Reset JARM data deletes the entire JARM data collection. Before this happens, you are warned by a system message. Confirming this option means that all measurement data for the framework is no longer available.