topic Re: Performance and Tuning in Application Development and Automation Discussions

Performance and Tuning

Former Member — Sat, 06 Jan 2007 21:18:19 GMT

Is Performance, tuning used to improve the runtime performance of Reports only ..Can I get more description of Performance and Tuning..........

Re: Performance and Tuning

RichHeilman — Sat, 06 Jan 2007 21:46:43 GMT

Performance tuning can be used in all ABAP developments, not just reporting, you could have a dialog transaction that performs poorly due do data access, or unnecessary processing of data.

Check transaction SE30 for the runtime analysis and the "Tips and Tricks" button.

Regards,

Rich Heilman

Re: Performance and Tuning

Former Member — Sat, 06 Jan 2007 21:50:11 GMT

Is there any documentation/link available where I can check this....

Re: Performance and Tuning

RichHeilman — Sat, 06 Jan 2007 21:56:17 GMT

http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp

http://www.erpgenie.com/abap/performance.htm

http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/abapPerformanceand+Tuning&

http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617cafe68c11d2b2ab080009b43351/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/d1/801f7c454211d189710000e8322d00/frameset.htm

Regards,

RIch Heilman

Re: Performance and Tuning

anversha_s — Sun, 07 Jan 2007 05:20:57 GMT

hi,

adding to the above.

SE30 - gives you a run time analysis and points out the issues more at design time.

ST05 - Is the most useful if you want to track time taken for execution of each of the sections.

SM50 - Will give you a work process overview, not sure at a program level how can it help you.

Some times you will have to use a combination of SE30 and ST05.

I would like to use St05 personally.

http://help.sap.com/saphelp_47x200/helpdata/en/f2/31adaa810c11d288ec0000e8200722/frameset.htm

Regards

Anver

Re: Performance and Tuning

Former Member — Sun, 07 Jan 2007 17:51:37 GMT

For some reason this is my favourite:

/people/rob.burbank/blog/2006/11/16/performance--what-will-kill-you-and-what-will-leave-you-with-only-a-flesh-wound

Rob

Re: Performance and Tuning

Former Member — Mon, 08 Jan 2007 01:42:13 GMT

What are available techniques available for Improving performance of Reports...

Re: Performance and Tuning

Former Member — Mon, 08 Jan 2007 08:45:41 GMT

Hi,

CHk this blog....

/people/rob.burbank/blog/2006/11/16/performance--what-will-kill-you-and-what-will-leave-you-with-only-a-flesh-wound

Here are some performance TIPS

LOOP AT with WHERE clause

Working with internal tables

For all entries

Tools for performance tuning

Using table buffering

LOOP AT with WHERE clause

If you use a LOOP AT statement with a WHERE clause, the table whole will be read through

and not only the entriers that satifies the WHERE clause. This can lead to performance

problems when a very large internal table is read many times with a WHERE clause.

The solution is to sort the table on the keyfields, use a READ statment to find

the first entry that satifies the key. Then you can start the loop here, and check for

changes in the keyfield to exit the loop.

Do not

loop at gi_mseg into g_mseg

where matnr = p_matnr and

werks = p_werks and

lgort = p_lgort and

sobkz = space,

endloop.

Instead use:

Sort internal table with entries from MSEG

sort gi_mseg by matnr werks lgort.

Find index of first entry that satifies the where clause

data:

l_tabix_from like sy-tabix.

read table gi_mseg with key matnr = p_matnr

werks = p_werks

lgort = p_lgort binary search

into g_mseg.

check sy-tabix > 0.

move sy-tabix to l_tabix_from.

Loop over the table from l_tabix_from, check for changes in keyfields, and

if necessary check other fields.

loop at gi_mseg into g_mseg from l_tabix_from.

if g_mseg-matnr <> p_matnr or

g_mseg-werks <> p_werks or

g_mseg-lgort <> p_lgort.

Stop loop

exit.

endif.

Check other fields

check g_mseg-sobkz = space.

..... do something ......

endloop.

For all entries

The for all entries creates a where clause, where all the entries in the driver table are combined with OR. If the number of entries in the driver table is larger than rsdb/max_blocking_factor, several similar SQL statements are executed to limit the length of the WHERE clause.

Some steps that might make FOR ALL ENTRIES more efficient:

- Removing duplicates from the the driver table

- Sorting the driver table

- If possible, convert the data in the driver table to ranges so a BETWEEN statement is used instead of and OR statement:

- FOR ALL ENTRIES IN i_tab

WHERE mykey >= i_tab-low and

mykey <= i_tab-high.

Tools for performance tuning

The runtime analysis (SE30)

SQL Trace (ST05)

Tips and Tricks tool

The performance database

Using table buffering

Using buffered tables improves the performance considerably. Note that in some cases a statement can not be used with a buffered table, so when using these staments the buffer will be bypassed. These staments are:

Select DISTINCT

ORDER BY / GROUP BY / HAVING clause

Any WHERE clasuse that contains a subquery or IS NULL expression

JOIN

A SELECT... FOR UPDATE

If you want to explicitly bypass the buffer, use the BYPASS BUFFER addition to the SELECT clause.

Regards,

Balaji

**Rewards if answers are useful

Re: Performance and Tuning

Former Member — Mon, 08 Jan 2007 08:52:48 GMT

Have a look at below link.

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d0db4c9-0e01-0010-b68f-9b1408d5f234">Performance Tuning Tips</a>

Best Regards,

Vibha

*Please mark all the helpful answers