<?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: figures for performance in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/figures-for-performance/m-p/3301113#M790275</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A.    The time needed for GuiXT is normally well below 30 milliseconds. &lt;/P&gt;&lt;P&gt;A good way for anyone (with SAP GUI 6.20 upwards) to measure these times is the following: In SAP GUI window, at the bottom right hand side, you can display various figures, notably: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Response time&lt;/P&gt;&lt;P&gt;- Interpretation time&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The response time is the response time of the application server (application including database calls, total roundtrip). &lt;/P&gt;&lt;P&gt;The interpretation time is the front end processing time including GuiXT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, you can do the following: Go to a certain screen and write down the time figures for each "Enter". Make a series of measurements to get more stable results. &lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;- Response time: 0.850 0.650 0.550 0.600 0.590&lt;/P&gt;&lt;P&gt;- Interpretation time: 0.050 0.040 0.040 0.030 0.030&lt;/P&gt;&lt;P&gt;Now deactivate GuiXT (in GuiXT window or in SAP GUI, since this doesn't make a significant difference). Measure again:&lt;/P&gt;&lt;P&gt;- Response time: 0.640 0.620 0.550 0.610 0.580&lt;/P&gt;&lt;P&gt;- Interpretation time: 0.050 0.040 0.050 0.040 0.040 &lt;/P&gt;&lt;P&gt;You will always notice that:&lt;/P&gt;&lt;P&gt;- the response time is essentially the same&lt;/P&gt;&lt;P&gt;- the interpretation time might increase a little bit (e.g. plus 0.02 sec). &lt;/P&gt;&lt;P&gt;In some cases, when you delete numerous fields in a complex screen, the time will even decrease (i.e., GuiXT saves some CPU cycles, since SAP GUI needs less time to display the screen). &lt;/P&gt;&lt;P&gt;The GuiXT overhead is often less than the time resolution used in SAP GUI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only if there are ABAP calls in the script will the interpretation time increase significantly, depending on the processing made in the called function. Or, if the scripts are on a slow network server, or web repository, the initial script loading takes some time. However, you can avoid this completely by using a local script cache.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Reward Points if found helpfull..&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Cheers,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Chandra Sekhar.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 02 Feb 2008 08:56:50 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-02T08:56:50Z</dc:date>
    <item>
      <title>figures for performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/figures-for-performance/m-p/3301112#M790274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Concerning the performance impact of using GuiXT with SAP GUI, can you produce some actual figures, i.e. processing time changes?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Mounika.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 Feb 2008 07:13:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/figures-for-performance/m-p/3301112#M790274</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-02T07:13:37Z</dc:date>
    </item>
    <item>
      <title>Re: figures for performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/figures-for-performance/m-p/3301113#M790275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A.    The time needed for GuiXT is normally well below 30 milliseconds. &lt;/P&gt;&lt;P&gt;A good way for anyone (with SAP GUI 6.20 upwards) to measure these times is the following: In SAP GUI window, at the bottom right hand side, you can display various figures, notably: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Response time&lt;/P&gt;&lt;P&gt;- Interpretation time&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The response time is the response time of the application server (application including database calls, total roundtrip). &lt;/P&gt;&lt;P&gt;The interpretation time is the front end processing time including GuiXT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, you can do the following: Go to a certain screen and write down the time figures for each "Enter". Make a series of measurements to get more stable results. &lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;- Response time: 0.850 0.650 0.550 0.600 0.590&lt;/P&gt;&lt;P&gt;- Interpretation time: 0.050 0.040 0.040 0.030 0.030&lt;/P&gt;&lt;P&gt;Now deactivate GuiXT (in GuiXT window or in SAP GUI, since this doesn't make a significant difference). Measure again:&lt;/P&gt;&lt;P&gt;- Response time: 0.640 0.620 0.550 0.610 0.580&lt;/P&gt;&lt;P&gt;- Interpretation time: 0.050 0.040 0.050 0.040 0.040 &lt;/P&gt;&lt;P&gt;You will always notice that:&lt;/P&gt;&lt;P&gt;- the response time is essentially the same&lt;/P&gt;&lt;P&gt;- the interpretation time might increase a little bit (e.g. plus 0.02 sec). &lt;/P&gt;&lt;P&gt;In some cases, when you delete numerous fields in a complex screen, the time will even decrease (i.e., GuiXT saves some CPU cycles, since SAP GUI needs less time to display the screen). &lt;/P&gt;&lt;P&gt;The GuiXT overhead is often less than the time resolution used in SAP GUI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only if there are ABAP calls in the script will the interpretation time increase significantly, depending on the processing made in the called function. Or, if the scripts are on a slow network server, or web repository, the initial script loading takes some time. However, you can avoid this completely by using a local script cache.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Reward Points if found helpfull..&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Cheers,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Chandra Sekhar.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 02 Feb 2008 08:56:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/figures-for-performance/m-p/3301113#M790275</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-02T08:56:50Z</dc:date>
    </item>
  </channel>
</rss>

