<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Performance issues in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202437#M1376274</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you run a SQL trace (ST05) or an ABAP runtime trace (SE30) on this program? If you could do that and then post the most expensive ABAP statements here, we would be able to help you much more efficiently. Even if you don't master those tools, simply monitoring the running program with SM50 might already give you an indication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a lot of "good practice" advice (see for example previous reply to your post) but some of the top performance killers in ABAP code are:&lt;/P&gt;&lt;P&gt;1) Expensive SELECT because WHERE clause cannot use a proper index&lt;/P&gt;&lt;P&gt;2) Expensive SELECT because of condition "WHERE field IN sel-options" and user has left sel-options list empty on the selection screen (result = select everything)&lt;/P&gt;&lt;P&gt;3) Expensive read access on a large internal table because of sequential read (missing BINARY SEARCH, or standard table used where sorted/hashed table would be needed)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a program times out, then those are the performance killers I would look out for first.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 Oct 2009 16:25:07 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-10-01T16:25:07Z</dc:date>
    <item>
      <title>Performance issues</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202434#M1376271</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I got requirement to increase te performance to one program which is written in 2006 by my old team mates.&lt;/P&gt;&lt;P&gt;I checked  in sm30..the load is very high and it is taking long time to execute as result ending in time out..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can soem one plz help me how to  proceed on this....&lt;/P&gt;&lt;P&gt;Any tips ..?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It wolud be a very great help..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks i&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Oct 2009 15:08:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202434#M1376271</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-01T15:08:22Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issues</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202435#M1376272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Avoid select*&lt;/P&gt;&lt;P&gt;2. Avoid select statement within loop.&lt;/P&gt;&lt;P&gt;3.Use field symbols instead of structures (e.g. loop at itab assigning &amp;lt;FS_name&amp;gt;)&lt;/P&gt;&lt;P&gt;4. If the program is updating some database table for multiple records then check it should be updated by internal table, not by single single record.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Oct 2009 15:32:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202435#M1376272</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-01T15:32:05Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issues</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202436#M1376273</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thanks gor u r reply,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you plz provide example for 4th point..it would be very help ful..&lt;/P&gt;&lt;P&gt;Thanks..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Oct 2009 15:34:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202436#M1376273</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-01T15:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issues</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202437#M1376274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you run a SQL trace (ST05) or an ABAP runtime trace (SE30) on this program? If you could do that and then post the most expensive ABAP statements here, we would be able to help you much more efficiently. Even if you don't master those tools, simply monitoring the running program with SM50 might already give you an indication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a lot of "good practice" advice (see for example previous reply to your post) but some of the top performance killers in ABAP code are:&lt;/P&gt;&lt;P&gt;1) Expensive SELECT because WHERE clause cannot use a proper index&lt;/P&gt;&lt;P&gt;2) Expensive SELECT because of condition "WHERE field IN sel-options" and user has left sel-options list empty on the selection screen (result = select everything)&lt;/P&gt;&lt;P&gt;3) Expensive read access on a large internal table because of sequential read (missing BINARY SEARCH, or standard table used where sorted/hashed table would be needed)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If a program times out, then those are the performance killers I would look out for first.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Oct 2009 16:25:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202437#M1376274</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-01T16:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: Performance issues</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202438#M1376275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please do not ask or answer questions like this. The OP should read the stickies at the top of the forum before posting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thread locked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Oct 2009 20:35:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/performance-issues/m-p/6202438#M1376275</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-01T20:35:25Z</dc:date>
    </item>
  </channel>
</rss>

