ISA Server 2006 + Average response time for Non Cached requests = performance issues?!?!?!

All,
I am in a predicament with internet browsing speeds...We have a 3rd party look after our line and internet facing f/w  so I cant troubleshoot them, so at the moment Im looking at ISA as the potential bottleneck - we have a fairly standard environment:
Internal > Local Host > Perimiter n/work > Firewall > Internet
I have been running custom reports on the ISA server to see what data can be collected - I have noticed that "Average response time for non cached requests" (traffic by time of day) can be as high as 76 seconds!!!!!! Cached hits are between .5
and 2 seconds.
I have also coonfigured a connectivity verifier which is also flagging slow connectivity, massively over the >5000ms and also reporting "cant resolve server name on occassions- and this is configured for
www.Microsoft.com --- DNS ???!?!, however I have looked through DNS (no obvious errors / config issues) which I can see 
I have run the BPA on ISA server to ensure its Health - - connectivity verifier errors flagged timeouts to microsoft.com as expected...
Can anyone advise any obvious areas to investigate as Im struggling! - as always the 3rd party have told us the internet pipe is fine :O

Problem resolved.
DNS forwarders have been changed on the ISA server / DNS and this has improved lookup speed considerably.
thanks all :)

Similar Messages

  • Average Response Times for a Reports Server

    On Application Server Control and Grid Control are sections listing the Average Response Time in milliseconds.
    Can anyone tell me what response it is measuring exactly?
    Thanks
    Andy

    See the Online Help for the page for a description of the metric. In Help, you can search for "metric" to see definitions of the other metrics.

  • Average Response Time for Reports

    Hi Gurus,
    I am using OAS 10.1.2.0.2 with Business Intelligence and Forms Installation.
    Previously I have never seen Average Response Time of Reports server greater than 10000(ms),
    But It is increasing continously and now within 2-3 days it has increased upto 114668(ms)
    CPU Usage (%)          N/A
         Memory Usage (MB)          N/A
         Average Response Time (ms)          114668
    its Maximum queue size is 1000....
    I am not able to find out why it is increasing in this manner.....
    plz help..
    Thanx

    Hi,
    Today it has been increased upto 170236 ...
    Thanx,
    Santosh

  • Average response times for VA01 and VA02 transactions

    Hi,
    we have some users complaining about response times, more specific for VA01 and VA02 transactions. We would like to compare our average response times to those of other companies in order to get an idea of what is acceptable to most companies. If you are willing to contribute, can you please send a few hours of STAD data (only for VA01 and VA02 transactions) of an average working day? Perhaps you can download the data into a spreadsheet and mail the zipped file to my account Many thanks.
    Best regards,
    Guido Van Leuven

    Hi,
    This is not the issue. We are investigating everything possible to improve our response times and we believe that that these are ok as well. We just want to build a case where we can prove that our response times are not worse than those at other companies and that we can do only by comparing those statistics.
    Best regards,
    Guido Van Leuven

  • ASM & Average Response Time

    Greetings All, I was hoping that others may have some insight into DB Control and how is reports ASM Disk response times.
    First my environment:
    Oracle RAC 11g R1 Standard Edition, Patchset 12
    Two Node Cluster
    Windows x64 2003 R2 DataCenter Edition.
    I am leveraging DB Control to monitor the ASM instances along with the db instances. My issue is regarding how db control gathers metrics to report on average response time for the DISKS that make up the Disk Group.
    I have two issues:
    1.) The overall response time reported in db control for my disk group "DATA" does not jive with the average I calculate based on the numbers being reported by db control. E.g.) I have ten LUNS in my DATA disk group and if I calculate the mean avg response time from each individual disk as reported by db control I don't get the same number being reported by db control. The numbers differ by as much as 20%.
    2.) The numbers reported by ASM for avg response time for each LUN in the disk group are not the same from disk to disk. E.g.) In my current production environment here are the Avg Response Times for each LUN in the group:
    8.73, 11.38, 5.22, 4.13, 3.04, 15.84, 12.71, 12.91, 10.51, 9.25.
    I would have expected that these disks would have had the same avg response time because ASM is working to guarantee that each disk has the same number of I/O's.
    The disk array has identical disks for all 10.
    Further, the average for all disks as being reported by db control is : 7.28.
    If I do the math I get an average of 9.38, the % diff between these two numbers is 28%
    I have heard that db control does a poor job of reporting on ASM disk metrics but this is just people grumbling. I was hoping that someone out there may have some solid facts regarding db control and ASM.

    hey....
    maybe its be better off to open a generel discussion task on metalink....
    *T                                                                                                                                                                               

  • Significant difference in response times for same query running on Windows client vs database server

    I have a query which is taking a long time to return the results using the Oracle client.
    When I run this query on our database server (Unix/Solaris) it completes in 80 seconds.
    When I run the same query on a Windows client it completes in 47 minutes.
    Ideally I would like to get a response time equivalent on the Windows client to what I get when running this on the database server.
    In both cases the query plans are the same.
    The query and plan is shown below :
    {code}
    SQL> explain plan
      2  set statement_id = 'SLOW'
      3  for
      4  SELECT DISTINCT /*+ FIRST_ROWS(503) */ objecttype.id_object
      5  FROM documents objecttype WHERE objecttype.id_type_definition = 'duotA9'
      6  ;
    Explained.
    SQL> select * from table(dbms_xplan.display('PLAN_TABLE','SLOW','TYPICAL'));
    PLAN_TABLE_OUTPUT
    | Id  | Operation          | Name      | Rows  | Bytes |TempSpc| Cost (%CPU)|
    |   0 | SELECT STATEMENT   |           |  2852K|    46M|       | 69851   (1)|
    |   1 |  HASH UNIQUE       |           |  2852K|    46M|   153M| 69851   (1)|
    |*  2 |   TABLE ACCESS FULL| DOCUMENTS |  2852K|    46M|       | 54063   (1)|
    {code}
    Are there are configuration changes that can be done on the Oracle client or database to improve the response times for the query when it is running from the client?
    The version on the database server is 10.2.0.1.0
    The version of the oracle client is also 10.2.0.1.0
    I am happy to provide any further information if required.
    Thank you in advance.

    I have a query which is taking a long time to return the results using the Oracle client.
    When I run this query on our database server (Unix/Solaris) it completes in 80 seconds.
    When I run the same query on a Windows client it completes in 47 minutes.
    There are NO queries that 'run' on a client. Queries ALWAYS run within the database server.
    A client can choose when to FETCH query results. In sql developer (or toad) I can choose to get 10 rows at a time. Until I choose to get the next set of 10 rows NO rows will be returned from the server to the client; That query might NEVER complete.
    You may get the same results depending on the client you are using. Post your question in a forum for whatever client you are using.

  • ISA server 2006 crashed after some times :(

    Hello.
    My ISA server is crashed. For
    example when my clients upload files to a remote server my upload speed is Reduced and
    server crashed :(. How can I troubleshoot it? It is
    ver vital for me and my clients are upset.
    Thank you and cheers.

    1. Some more information is needed. Your description of proble is incomplete and no one can guess what has happened.
    2. Find some material evidence - like Event logs and fw logs
    3. There is a special diskussion on ISA server in forum
    http://forums.isaserver.org/ and trobleshooting procedures in
    http://www.isaserver.org/
    4. For troubleshooting read
    http://support.microsoft.com/kb/943462
    http://technet.microsoft.com/en-us/library/bb794787.aspx
    http://technet.microsoft.com/en-us/library/bb794753.aspxhttp://blogs.technet.com/b/yuridiogenes/archive/2010/01/20/troubleshooting-isa-server-2006-performance-issues-webcast-for-ms-partners.aspx
    Regards
    Milos

  • CVU failing with error msg(PRVF-5636 : The DNS response time for an unreach

    I am installing 4Node 10g RAC on OEL5.3, i downloaded CU from OTN and getting below warning messages.
    Checking the file "/etc/resolv.conf"; to make sure only one of domain and search entries is defined
    File "/etc/resolv.conf"; does not have both domain and search entries defined
    Checking if domain entry in file "/etc/resolv.conf"; is consistent across the nodes...
    domain entry in file "/etc/resolv.conf"; is consistent across nodes
    Checking if search entry in file "/etc/resolv.conf"; is consistent across the nodes...
    search entry in file "/etc/resolv.conf"; is consistent across nodes
    Checking file "/etc/resolv.conf"; to make sure that only one search entry is defined
    All nodes have one search entry defined in file "/etc/resolv.conf";
    Checking all nodes to make sure that search entry is "soft1" as found on node "racnode4"
    All nodes of the cluster have same value for 'search'
    Checking DNS response time for an unreachable node
    Node Name Status
    racnode4 failed
    racnode3 failed
    racnode2 failed
    racnode1 failed
    PRVF-5636 : The DNS response time for an unreachable node exceeded "15000" ms on following nodes: racnode4,racnode3,racnode2,racnode1
    File "/etc/resolv.conf"; is not consistent across nodes
    Check: Time zone consistency
    Result: Time zone consistency check passed
    Pre-check for cluster services setup was unsuccessful on all the nodes.
    [oracle@racnode1 bin]$

    PRVF-5636 : The DNS response time for an unreachable node exceeded "15000" ms on following nodes: racnode4,racnode3,racnode2,racnode1 have you checked this note? Runcluvfy - Dns Response Time Check - Fails with PRVF-5636 The DNS response time for an unreachable node exceeded "15000" ms [ID 1326997.1]
    Also have you set Domain name on all servers?
    [root@oracle-ha ~]# domainname
    (none)
    [root@oracle-ha ~]# domainname ckpt.com
    [root@oracle-ha ~]# domainname
    ckpt.com
    [root@oracle-ha ~]#You can check DNS configuration of your setup using this link http://computernetworkingnotes.com/network-administrations/dns-server.html

  • PRVF-5636 : The DNS response time for an unreachable node exceeded "15000"

    Friends,
    OS: OEL 6.3 64 bit
    DB: 11.2.0.3
    Environment: VirtualBox 4.1.20
    i have 3 nodes. one is for dns and other two for rac1 and rac2
    i have done all the preliminary steps. then i started
    [oracle@rac1 grid]$ ./runcluvfy.sh stage -pre crsinst -n rac1,rac2 -verboseand all are passed except the above subjected error.
    Checking DNS response time for an unreachable node
      Node Name                             Status                 
      rac2                                  failed                 
      rac1                                  failed                 
    PRVF-5636 : The DNS response time for an unreachable node exceeded "15000" ms on following nodes: rac2
    File "/etc/resolv.conf" is not consistent across nodesok....now to solve this error...i tried many options...but not able to succeed.
    Try 1:
    [root@mydns ~]# time nslookup rac1
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   rac1.sathy.net
    Address: 192.168.1.3
    real    0m0.051s
    user    0m0.003s
    sys     0m0.011s
    [root@mydns ~]# [oracle@rac1 grid]$ time nslookup mydns
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   mydns.sathy.net
    Address: 192.168.1.2
    real    0m0.019s
    user    0m0.005s
    sys     0m0.008s
    [oracle@rac1 grid]$
    [root@rac2 ~]# time nslookup rac1
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   rac1.sathy.net
    Address: 192.168.1.3
    real    0m0.019s
    user    0m0.008s
    sys     0m0.005s
    [root@rac2 ~]# Try 2:
    [root@mydns ~]# nslookup sathy-scan
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   sathy-scan.sathy.net
    Address: 192.168.1.8
    Name:   sathy-scan.sathy.net
    Address: 192.168.1.9
    Name:   sathy-scan.sathy.net
    Address: 192.168.1.7
    [root@mydns ~]# nslookup rac1
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   rac1.sathy.net
    Address: 192.168.1.3
    [root@mydns ~]# nslookup rac2
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   rac2.sathy.net
    Address: 192.168.1.5
    [root@mydns ~]#
    [oracle@rac1 grid]$ nslookup sathy-scan
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   sathy-scan.sathy.net
    Address: 192.168.1.9
    Name:   sathy-scan.sathy.net
    Address: 192.168.1.7
    Name:   sathy-scan.sathy.net
    Address: 192.168.1.8
    [oracle@rac1 grid]$ nslookup rac2
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   rac2.sathy.net
    Address: 192.168.1.5
    [oracle@rac1 grid]$ nslookup rac1
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   rac1.sathy.net
    Address: 192.168.1.3
    [oracle@rac1 grid]$
    [root@rac2 ~]# nslookup sathy-scan
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   sathy-scan.sathy.net
    Address: 192.168.1.7
    Name:   sathy-scan.sathy.net
    Address: 192.168.1.8
    Name:   sathy-scan.sathy.net
    Address: 192.168.1.9
    [root@rac2 ~]# nslookup rac1
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   rac1.sathy.net
    Address: 192.168.1.3
    [root@rac2 ~]# nslookup rac2
    Server:         192.168.1.2
    Address:        192.168.1.2#53
    Name:   rac2.sathy.net
    Address: 192.168.1.5
    [root@rac2 ~]# Try 3:
    [root@mydns ~]# cat /etc/named.conf
    // Default named.conf generated by install of bind-9.2.4-30.el4_7.2
    options {
            listen-on port 53 { any; };
            directory "/var/named";
            dump-file "/var/named/data/cache_dump.db";
            statistics-file "/var/named/data/named_stats.txt";
            forwarders { 192.168.1.1; };
    include "/etc/rndc.key";
    zone "sathy.net" IN {
    type master;
    file "sathy.net.zone";
    allow-update { none; };
    zone "1.168.192.in-addr.arpa." IN {
    type master;
    file "1.168.192.in-addr.arpa";
    allow-update { none; };
    zone "." in {
    type hint;
    file "/dev/null";
    [root@mydns ~]# Try 4:
    [root@mydns ~]# cat /etc/selinux/config
    # This file controls the state of SELinux on the system.
    # SELINUX= can take one of these three values:
    #     enforcing - SELinux security policy is enforced.
    #     permissive - SELinux prints warnings instead of enforcing.
    #     disabled - No SELinux policy is loaded.
    SELINUX=disabled
    # SELINUXTYPE= can take one of these two values:
    #     targeted - Targeted processes are protected,
    #     mls - Multi Level Security protection.
    #SELINUXTYPE=targeted
    [root@mydns ~]#
    [oracle@rac1 grid]$ cat /etc/selinux/config
    # This file controls the state of SELinux on the system.
    # SELINUX= can take one of these three values:
    #     enforcing - SELinux security policy is enforced.
    #     permissive - SELinux prints warnings instead of enforcing.
    #     disabled - No SELinux policy is loaded.
    SELINUX=disabled
    # SELINUXTYPE= can take one of these two values:
    #     targeted - Targeted processes are protected,
    #     mls - Multi Level Security protection.
    #SELINUXTYPE=targeted
    [oracle@rac1 grid]$
    [root@rac2 ~]# cat /etc/selinux/config
    # This file controls the state of SELinux on the system.
    # SELINUX= can take one of these three values:
    #     enforcing - SELinux security policy is enforced.
    #     permissive - SELinux prints warnings instead of enforcing.
    #     disabled - No SELinux policy is loaded.
    SELINUX=disabled
    # SELINUXTYPE= can take one of these two values:
    #     targeted - Targeted processes are protected,
    #     mls - Multi Level Security protection.
    #SELINUXTYPE=targeted
    [root@rac2 ~]# what else i have to check to solve this error?
    for the past 2 days..i am trying to solve this error. may be somewhere a small mistake is happened from my side, but i am not able to find out.
    hope somebody will find out and help me.
    thanks

    ok...here it is....
    [root@mydns ~]# cat /etc/resolv.conf
    # Generated by NetworkManager
    search sathy.net
    nameserver 192.168.1.2
    [root@mydns ~]#
    [root@rac1 ~]# cat /etc/resolv.conf
    # Generated by NetworkManager
    search sathy.net
    nameserver 192.168.1.2
    [root@rac1 ~]#
    [root@rac2 ~]# cat /etc/resolv.conf
    # Generated by NetworkManager
    search sathy.net
    nameserver 192.168.1.2
    [root@rac2 ~]#
    [root@mydns ~]# cat /etc/hosts
    #127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
    #::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
    127.0.0.1               localhost.localdomain localhost
    ::1            localhost6.localdomain6 localhost6
    # Public Network – (eth0)
    192.168.1.3     rac1.sathy.net    rac1
    192.168.1.5     rac2.sathy.net    rac2
    # Public Virtual IP (VIP) addresses – (eth0:1)
    192.168.1.4     rac1-vip.sathy.net rac1-vip
    192.168.1.6     rac2-vip.sathy.net rac2-vip
    # Private Interconnect – (eth1)
    192.168.2.3      rac1-priv.sathy.net       rac1-priv
    192.168.2.5      rac2-priv.sathy.net       rac2-priv
    #Compute Node Client Access SCAN Interface details
    #192.168.1.7   sathy-scan.sathy.net  sathy-scan
    #192.168.1.8   sathy-scan.sathy.net  sathy-scan
    #192.168.1.9   sathy-scan.sathy.net  sathy-scan
    [root@mydns ~]#
    [root@rac1 ~]# cat /etc/hosts
    #127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
    #::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
    127.0.0.1               localhost.localdomain localhost
    ::1            localhost6.localdomain6 localhost6
    # Public Network – (eth0)
    192.168.1.3     rac1.sathy.net    rac1
    192.168.1.5     rac2.sathy.net    rac2
    # Public Virtual IP (VIP) addresses – (eth0:1)
    192.168.1.4     rac1-vip.sathy.net rac1-vip
    192.168.1.6     rac2-vip.sathy.net rac2-vip
    # Private Interconnect – (eth1)
    192.168.2.3      rac1-priv.sathy.net       rac1-priv
    192.168.2.5      rac2-priv.sathy.net       rac2-priv
    #Compute Node Client Access SCAN Interface details
    #192.168.1.7   sathy-scan.sathy.net  sathy-scan
    #192.168.1.8   sathy-scan.sathy.net  sathy-scan
    #192.168.1.9   sathy-scan.sathy.net  sathy-scan
    [root@rac1 ~]#
    [root@rac2 ~]# cat /etc/hosts
    #127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
    #::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
    127.0.0.1               localhost.localdomain localhost
    ::1            localhost6.localdomain6 localhost6
    # Public Network – (eth0)
    192.168.1.3     rac1.sathy.net    rac1
    192.168.1.5     rac2.sathy.net    rac2
    # Public Virtual IP (VIP) addresses – (eth0:1)
    192.168.1.4     rac1-vip.sathy.net rac1-vip
    192.168.1.6     rac2-vip.sathy.net rac2-vip
    # Private Interconnect – (eth1)
    192.168.2.3      rac1-priv.sathy.net       rac1-priv
    192.168.2.5      rac2-priv.sathy.net       rac2-priv
    #Compute Node Client Access SCAN Interface details
    #192.168.1.7   sathy-scan.sathy.net  sathy-scan
    #192.168.1.8   sathy-scan.sathy.net  sathy-scan
    #192.168.1.9   sathy-scan.sathy.net  sathy-scan
    [root@rac2 ~]#
    [oracle@rac1 ~]$ ssh rac2 date
    Sun Sep  9 22:04:45 IST 2012
    [oracle@rac1 ~]$ su - grid
    Password:
    [grid@rac1 ~]$ ssh rac2 date
    Sun Sep  9 22:04:54 IST 2012
    [grid@rac1 ~]$
    [oracle@rac2 ~]$ ssh rac1 date
    Sun Sep  9 22:04:18 IST 2012
    [oracle@rac2 ~]$ su - grid
    Password:
    [grid@rac2 ~]$ ssh rac1 date
    Sun Sep  9 22:04:31 IST 2012
    [grid@rac2 ~]$ Now the error is ...
    PRVF-5637 : DNS response time could not be checked on following nodes: rac2,rac1what else?
    i wonder how it was successful in my previous installation which in oel 5.7....
    Edited by: OraDB on Sep 9, 2012 9:44 AM

  • High Avg Response time for logon requests via CMS

    Hi Team ,
    We are continuously receiving observing high Average reponse time for logon requests to the BO system  via  Central Management Server.
    We observe response time up to 25043 ms .
    Currently we are on SAP BO 4.0  SP7 patch 9  (4.0.7.9)
    DB = SQL server 2008 R2
    App Server = SAP NW 7.31 SP 7.
    Also the size of our CMS DB is around 15 GB .
    What could be  the possible reasons ?
    Regards ,
    Abhinav

    Hi Abhinav,
    As one of the issues has been raised as a bug which is resolved in BI 4.1 so you can upgrade to resolve this bug. Also if the CMS database size is large then CMS has to search for objects through huge number of rows hence that will affect overall performance. So you can try to reduce this size as per my previous upate.
    Apart this you can try following steps
    Try to ping CMS DB server from BO servers and confirm the response is coming in 1 ms. Run tracert <DB servers name> from CMD and check the number of hops. If response time is not 1 ms or there are more number of hops then ask your network team to resolve network latency issue
    You can increase the "System database connections"  for each CMS from server properties. It is set to 14 by default which means the CMS will establish 14 connections to CMS database at any time. You can increase this value, however please make sure that the system database allows more connections than default 14 from DB side. This needs to be confirmed from your DBA.
    Please add CMS cluster members in platformservices.properties file under Tomcat folder. Please refer following SAP KBA for steps to add the cluster members
           http://service.sap.com/sap/support/notes/1668515
           http://service.sap.com/sap/support/notes/1766935    
       4. Also please confirm number of users simultaneously login to system at peak time. Usually one           CMS is capable of handling around 500 requests. So if you have more then 1000 users then add           another new CMS on same nodes if there is enough free memory on the server
    Regards,
    Hrishikesh

  • ISA Server 2006

    Hello,
    How can I determine how our ISA Server 2006 boxes are being utilized within our organization? The original Exchange 2003 admin left the company years ago and now I am here trying to prepare for our upgrade to Exchange 2010.
    Any help will be greatly appreciated.
    Thank you,
    Sandy

    Look at the firewall logs (for ALL traffic) to see if there is any activity at all for a period of time.
    This should be sufficient to determine if the box is still be used at all.
    https://technet.microsoft.com/en-us/library/bb794817.aspx?f=255&MSPPError=-2147217396
    Blog: http://theinfraguys.com
    Follow me at Facebook
    The Infra Guys Facebook Page
    Join the Singapore System Center Admin Group
    SG System Center Admin Group
    Please remember to click Mark as Answer on the answer if it helps you in anyway

  • Incorrect Alerts CPU Time and Average Response Time

    BUG
    My Alert on Web app is consistently behaving incorrectly.
    If I set an alert to monitor CPU Time at threshold 1.5 seconds, it's actually set to 1.5 milliseconds even though the graph shows a dotted red line at 1.5 seconds. The alert will trigger at 1.5 milliseconds threshold. So, instead, I have to set threshold
    to 1500 seconds - the graph is completely useless showing a red dotted line at ~24 mins but the alert does then go off when CPU time goes above 1500 ms (aka 1.5 seconds).
    The original portal alert seems to be fine - this problem is on new portal only. Unaffected by browser type - all browsers do the same thing (Just has to be said before someone asks).
    This seems to apply to all metrics using seconds (Average Response Time acts in the same way)

    Hii...
    Am sure you are much aware " Components Response Time spectrum"
    ########Analyzing Performance Problems#################
    --High wait time: Insufficient number of free work processes
    --High roll-wait time: Communication problem with GUI, external system,
    or large amount of data requested
    --High load and generation time: SAP buffers (Program, CUA or Screen)
    too small
    --High database request time: CPU/memory bottleneck on database server;
    communication problem with database server, expensive SQL statements,
    database locks, missing indexes, missing statistics or small database buffer(s)
    --High CPU time: Expensive ABAP processing, for example, processing
    large tables; inefficient programming
    --Processing time more than twice CPU time: CPU bottlenecks
    If time aloows look at
    Note 0000008963 - Definition of SAP response time/processing time/CPU time
    Rgds

  • Report to calculate avg response time for a transaction using ST03.

    Hi Abap Gurus ,
    I want to develop a report which calculates the average response time(ST 03) for a transaction on hourly basis.
    I have read many threads like in which users are posting which tables/FM to use to extract data such as  dialog step and total response time .
    I am sure many would have created a report like this , would appeciate if you can share pseudo code for same.Any help regarding the same is highly appreciated...
    Cheers,
    Karan

    http://jakarta.apache.org/jmeter/

  • Strange response time for an RFC call viewed from STAD on R/3 4.7

    Hello,
    On our R/3 4.7 production system, we have a lot of external RFC calls to execute an  abap module function. There are 70 000 of these calls per day.
    The mean response time for this RFC call is 35 ms.
    Some times a few of them (maybe 10 to 20 per day) are way much longer.
    I am currently analysing with STAD one of these long calls  which lasted 10 seconds !
    Here is the info from STAD
    Response time :                10 683 ms
    Total time in workprocess : 10 683 ms
    CPU time  :                               0 ms
    RFC+CPIC time :                       0 ms
    Wait for work process           0 ms
    Processing time           10.679 ms
    Load time                            1 ms
    Generating time                   0 ms
    Roll (in) time                        0 ms
    Database request time         3 ms
    Enqueue time                      0 ms
    Number      Roll ins            0
                     Roll outs           0
                     Enqueues         0
    Load time   Program             1  ms
                      Screen              0  ms
                     CUA interf.          0  ms
    Roll time    Out                 0  ms
                      In                  0  ms
                    Wait                0  ms
    Frontend    No.roundtrips       0   
                      GUI time            0  ms
                      Net time            0  ms
    There is nearly no abap processing in the function module.
    I really don't uderstand what is this  10 679 ms processing time especially with 0 ms cpu time and 0 ms wait time.
    A usual fast RFC call gives this data
    23 ms response time
    16 ms cpu time
    14 ms processing time
    1 ms load time
    8 ms Database request time
    Does anybody have an idea of what is the system doing during the 10 seconds  processing time ?
    Regards,
    Olivier

    Hi Graham,
    Thank you for your input and thoughts.
    I will have to investigate on RZ23N and RZ21 because I'm not used to use them.
    I'm used to investigate performance problems with ST03 and STAD.
    My system is R/3 4.7 WAS 6.20. ABAP and BASIS 43
    Kernel 6.40 patch level 109
    We know these are old patch levels but we are not allowed to stop this system for upgrade "if it's not broken" as it is used 7/7 24/24.
    I'm nearlly sure that the problem is not an RFC issue because I've found other slow dialog steps for web service calls and even for a SAPSYS technical dialog step  of type <no buffer>. (what is this ?)
    This SAPSYS dialog step has the following data :
    User : SAPSYS
    Task type : B
    Program : <no buffer>
    CPU time                       0 ms
    RFC+CPIC time              0 ms
    Total time in workprocs    5.490 ms
    Response time               5.490 ms
    Wait for work process           0 ms
    Processing time             5.489 ms
    Load time                            0 ms
    Generating time                   0 ms
    Roll (in+wait) time                0 ms
    Database request time          1 ms ( 3 Database requests)
    Enqueue time                       0 ms
    All hundreds of other SAPSYS <no buffer> steps have a less than 5 ms response time.
    It looks like the system was frozen during 5 seconds...
    Here are some extracts from STAD of another case from last saturday.
    11:00:03     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     13     13     0     0
    11:00:03     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:04     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     16
    11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     77     77     0     16
    11:00:04     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     16
    11:00:05     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     16
    11:00:05     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     53     53     0     0
    11:00:06     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     76     76     0     0
    11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     20     20     0     31
    11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     0
    11:00:06     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     13     13     0     0
    11:00:06     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     34     34     0     16
    11:00:07     bt1sqkvh_PLG_18      RFC     R     0     USER_LECDIS     15     15     0     0
    11:00:07     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     13     13     0     16
    11:00:07     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     0
    11:00:07     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     23     13     10     0
    11:00:07     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     38     38     0     0
    11:00:08     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     20     20     0     16
    11:00:09     bt1sqkvg_PLG_18      RFC     R     0     USER_LECDIS     9 495     9 495     0     16
    11:00:09     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     9 404     9 404     0     0
    11:00:09     bt1sqkvh_PLG_18      RFC     R     1     USER_LECKIT     9 181     9 181     0     0
    11:00:10     bt1fsaplpr02_PLG RFC     R     3     USER_LECDIS     23     23     0     0
    11:00:10     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     8 465     8 465     0     16
    11:00:18     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     18     18     0     16
    11:00:18     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     89     89     0     0
    11:00:18     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     75     75     0     0
    11:00:18     bt1sqkvh_PLG_18      RFC     R     1     USER_LECDIS     43     43     0     0
    11:00:18     bt1sqk2t_PLG_18      RFC     R     1     USER_LECDIS     32     32     0     16
    11:00:18     bt1sqkvg_PLG_18      RFC     R     1     USER_LECDIS     15     15     0     16
    11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     0
    11:00:18     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     69     69     0     16
    11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     49     49     0     16
    11:00:18     bt1sqkve_PLG_18     RFC     R     5     USER_LECKIT     19     19     0     16
    11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     15     15     0     16
    The load at that time was very light with only a few jobs starting :
    11:00:08 bt1fsaplpr02_PLG RSCONN01                     B 31 USER_BATCH     39
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 31 USER_BATCH     34
    11:00:08 bt1fsaplpr02_PLG /SDF/RSORAVSH                B 33 USER_BATCH     64
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 33 USER_BATCH     43
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 34 USER_BATCH     34
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 35 USER_BATCH     37
    11:00:09 bt1fsaplpr02_PLG RVV50R10C                    B 34 USER_BATCH     60
    11:00:09 bt1fsaplpr02_PLG ZLM_HDS_IS_PURGE_RESERVATION B 35 USER_BATCH    206
    I'm thinking also now about the message server as there is load balancing for each RFC call ?
    Regards,
    Olivier

  • Average response Time

    All,
    What is the ideal Avg Response Time for a System?
    Is there any formula to calculate?
    What does SAP reccomend?

    Dear Bidwan,
      Response time for dialog process is <b>generally based on sum of wait timeroll in timeload generation timeprocessing timelock time+db request time</b> and is measured at the application server level.
    U can get these values from ST03(N) transaction.
    Response time will differ for different systems, there is no such thing as ideal response time. System can be tuned to get any value for response time based on system resources and system load.
    reward points if usefull.
    Awaiz.

Maybe you are looking for