Skip to Content
author's profile photo Former Member
Former Member

Looking for the cause of high processing time

Hi,

we now have a problem in production where at some times during the day, the response times of transactions on a particular application server get much higher than the normal.

We have looked at stad (workload) at these times and noticed an increase in processing time but not in cpu time.

We looked at the machine statistics and nothing was out of order at those times. (cpu, network, etc).

What is also strange is that we have other application servers running on the same machine which do not have the problem.

The question is how can we find out in which component is this processing time taking place ?

In what components can processing time happen ?

Thank you.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on May 16, 2008 at 08:09 PM

    Start looking through the reports in ST03N. One thing that helps to sift out what processes are hogging resources is to take a look at one of the reports like Response time distribution.

    Generally, I take the results from this and graph them in Excel to get a better idea of what type of process is using resources. When you overlay RFC, background, and DIA you will start to see if there are any correlations between processes (like background and RFC processes with response times that are nearly equal).

    Have you checked DB locks to see if you might having a contention issue at this time?

    Just wondering.

    J. Haynes

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Thank you.

      I don't think the database is the cause of the problems because we have other instances that access the same databse which don't have the high processing time statistics.

      Also, in st03n, we can't see the processing time.

      Thanks for the group, I didn't notice it.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.