cpu time elapsed time
The analysis of ABAP runtime allows you to analyze the time to execute the various objects such as transactions, programs and function modules, or sub-objects, such as modular units or commands. An analysis of ABAP implementation is particularly useful for the individual objects that are CPU intensive (see analysis of the workload).
An analysis of ABAP implementation consists of three phases:
1. By limiting the data as: In this stage, you decide what is the object of analysis. You decide the type of aggregation is used (total aggregation, aggregation of the position of call, not cumulative) and whether to use filtering options (for modularization units or orders).
2. Data to measure: You can measure and record data running time is of the same user session in which the analysis of ABAP runtime is underway, or in a separate user session. You can also start the runtime analysis of ABAP for R / 3 work process and register data runtime for an object that is generated by this process work.
3. Data analysis: When using the full aggregation to analyze the data in the results list, which provides a record of registration for each unit called modularization or teaching. For performance analysis using a combination or aggregation of station call, there Other lists of events, such as lists of results table or hierarchy of call.
To access the initial screen of the analysis of the application in any ABAP R / 3 screen, select System>> Utilities>> Runtime analysis>> Run.
The runtime results of the analysis are recorded in an operating system file in the application server from a maximum of 8 days or transferred to the interface. Result file can be loaded into the runtime analysis of the ABAP interface at any time.
The system R / 3 ABAP parameter / Atrasizequota specifies the amount of memory should be reserved in the file system to store data results. The R / 3 parameter ABAP / atrapath states where the outcome data are stored in the file system. In the Description field, type a short text to identify your analysis.
In the area of the screen in the current session, select and specify the object to be analyzed. To run the object, select Run. Alternatively use a separate user session to access an R / 3 work processes (see the slide show execution data).
Limit data to display:
Part of the program tab you can restrict the data record specific parts of the program. To do this, you must specify the program and its type (program, world class or routine), and the procedure to be measured. By selecting within and down, extending the registration data to include parts of the program and instructions of the program components you specify.
You can also limit data recorded by the choice of specific units. This allows you to save data between two fixed points, instructions and SET ABAP RUNTIME Analyzer TIME ANALYZER OFF, or between points such as dynamic menu options Runtime analysis → Switch ON (code RON transaction) or Runtime analysis → Shut Down (ROF Transaction Code).
In Duration and type You can specify the maximum size of the results and the recording time Max. Select the level of aggregation. Wide selection of aggregation causes must be a record created for each part of the program or instruction. The selection of the position of call aggregation causes a record that was created in the output file for each call station. Selection of any aggregation produces a record must be written to the file results for each call.
The runtime analysis of ABAP is normally used with a top-down procedure. First, save the data for an object individual, adding up the total and identify critical areas of programs and instructions. Then, limit the data recorded in the critical parts of programs and instructions, and adjust the level of aggregation called by the position or any combination of more detailed information.
http://abapreports.blogspot.com
http://testingcorner.blogspot.com
CFinder Capabilities and Usage
Tags: cpu, oracle, sql server cpu time elapsed time, statspack, time, windows
Leave a Comment