topic Re: HELP--PERFORMANCE TUNING in Application Development and Automation Discussions

HELP--PERFORMANCE TUNING

Former Member — Sat, 30 Dec 2006 10:06:41 GMT

Hi all,

Please help me in performance tuning.

Guide me to the documents and books that are useful for performance tuning of a R/3, ABAP and a JAVA systems.

As im a fresher ill be happy to start with the basics of performance tuning that too of a R/3 system.

Please send me the links of documents and e-books that relate to this matter.

Expecting your kind response.

Vineeth

Re: HELP--PERFORMANCE TUNING

Manohar2u — Sat, 30 Dec 2006 10:09:40 GMT

Refer to this link

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

Re: HELP--PERFORMANCE TUNING

Former Member — Sat, 30 Dec 2006 17:33:07 GMT

Hi,

you can aslo see some examples in Transaction Code - SE30. In this code go to Tips & Tricks..

Ashven

Re: HELP--PERFORMANCE TUNING

Former Member — Sat, 30 Dec 2006 18:04:34 GMT

Check:

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

and its links.

Rob

Re: HELP--PERFORMANCE TUNING

SantoshKallem — Mon, 01 Jan 2007 06:16:41 GMT

http://www.sap-img.com/abap/abap-fine-tuning.htm

http://www.allsaplinks.com/performanc_tuning.html

Happy New Year..

Reward If Helpful.

Cheers..

Santhosh Reddy

Re: HELP--PERFORMANCE TUNING

Former Member — Tue, 02 Jan 2007 02:47:51 GMT

Hi Vineeth,

You can find realted to this topic by searching through this

website.

www.esnips.com

Regards,

Balaji Reddy G

**Rewards if answers are useful

Re: HELP--PERFORMANCE TUNING

Former Member — Tue, 02 Jan 2007 11:16:41 GMT

Hi Vineeth,

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,

Ramamurthy

**Rewards if answers are useful