If you want to monitor the performance of your system, or compare its performance at different times, you can perform a runtime analysis. You usually start the runtime analysis (after performing certain activities in the system) with transaction SE30.
You use transaction SICF to activate the runtime analysis both for ICF runtime and for applications that run using ICF runtime. You can evaluate the results with transaction SE30.
Activities
Activate the Runtime Analysis
Start the runtime analysis with transaction SICF.
Choose
.Enter the service path that you want the runtime analysis to be activated for.
You can set the option User-Dependent to activate the runtime analysis for a specific user or client (all users in a client) You can also implement a measurement variant. To do this, you need to enter the variant user (owner of the variant), the variant itself, and the measurement precision.
Any active runtime analyses must be deactivated after the requests have been executed. You deactivate the requests in transaction SICF by choosing Edit -> Runtime Analysis -> Deactivate.
Display/Evaluate Result
You can now evaluate the recorded runtime measurements in transaction SE30..
If you set the User-dependent flag when activating the runtime analysis in transaction SICF, the measurement results will be stored under the corresponding user. The entries are then stored in transaction SE30 under the user with which you performed the requests. If the option User-Dependent is not active, the entries are saved under pseudo user SAPSYS.
You can find the measurement entries for specific users in transaction SE30 under . Enter the relevant user name here and choose Enter.
Select the files that you want to display and choose Analyze (Evaluate). The subsequent graphic shows you the runtimes for the various main components (program environment, database, system).
By choosing Goto, you can call various hit lists, which display the runtimes for the various functions and methods separately or by category.
By choosing [OBJ] Sort, you can sort the displayed elements according to runtime. This helps you to see which method and function calls are the most time-consuming.
For detailed information about ABAP runtime analysis in transaction SE30, see:
Runtime Analysis