difference between slin, st05, and se30

[Former Member]

whats the difference between slin , st05 ans se30 t codes for performance tuning?

[former_member194613]

If you call them you will see that they are completely different

SLIN, you mean the code inspector functionality, checks code, extensive but based on code not execution

SE30 checks ABAP functions, measures all contributions to the whole program execution, what takes longest should be optimized

/people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy

ST05 check DB part, gives a lot of advise, see

/people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy

Siegfried

[Former Member]

Hi

In SLIN u get all the errors, warining messages for a particular program.

St05 wil give the performance of sql satements in the program.

SE30 gives the the execution time of the program .

[Former Member]

Hi

All these 3 Tools for Performance Analysis...

Run time analysis transaction SE30

SQL Trace transaction ST05

Extended Program Check (SLIN)

Along with these we can use Code Inspector ( SCI) also.

Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.

SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.

The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.

The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.

To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.

Extended Program Check

This can be called in through transaction SE38 or through transaction SLIN. This indicates possible problems that may cause performance problems.

Code Inspector (SCI)

You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).

The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.

Run time analysis transaction SE30

In Transaction SE30, fill in the transaction name or the program name which needs to be analyzed for performance tuning.

For our case, let this be “ZABAP_PERF_TUNING”

After giving the required inputs to the program, execute it. After the final output list has been displayed, PRESS the “BACK” button.

On the original SE30 screen, now click on “ANALYZE” button.

The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.

SQL Trace – ST05

Starting the Trace:

To analyze a trace file, do the following:

...

Choose the menu path Test  Performance Trace in the ABAP Workbench or go to Transaction ST05. The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.

Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).

If you want to switch on the trace under your user name, choose Trace on. If you want to pass on values for one or several filter criteria, choose Trace with Filter. Typical filter criteria are: the name of the user, transaction name, process name, and program name.

Now run the program to be analyzed.

Stopping the Trace:

To deactivate the trace:

...

Choose Test Performance Trace in the ABAP Workbench. The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.

Select the trace functions that you want to switch off.

Choose Deactivate Trace. If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-

Analyzing a Sample trace data:

PREPARE: Prepares the OPEN statement for use and determines the access method.

OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.

FETCH: Moves the cursor through the dataset created by the OPEN operation. The array size displayed beside the fetch data means that the system can transfer a maximum package size of 392 records at one time into the buffered area.

Hope it helps..

Regards,

KK

[former_member230674]

hai

kumar,

ST05 : The performance trace (ST05) record the following actions

-> Database calls

-> Lock management calls

-> Internal report and transaction calls

-> Remote calls

and display the logged measurement results in lists.

SLIN: is used to perform extended program check(EPC) and display appropriate warnings, errors and information messages whereever necessary in creating a package.

You can perform EPC checks on active sources only.

*SE30: Runtime Analysis

-> To monitor the performance of your system,

-> To compare its performance at different times.

You should find the following information:

1. Excessive or unnecessary use of modularization units

2.CPU-intensive program functions

3.User-specific functions that could be replaced with ABAP

statements

4.Inefficient or redundant database access.

It helps in analysing the performance of various programming concpts properly or not w.r.t database and modularisation and

cpu utilisation.

if useful, reward points.

bye

G.V.K.Prasad

Edited by: PRASAD GVK on Apr 13, 2008 3:01 PM

[Former Member]

Hi,

SLIN: When we r working on upgrade like upgrade from one version to other version to find Errors and information messages we use SLIN T-Code.

SE30 : This T-Code is used for Runtime Analysis

ST05 : This T-Code is used for performance issues.