STAD analysis - Please help for comparision

[former_member201054]

I am seeing more response time in below screenshot and want to compare with standard threshold value.

[former_member182967]

Hi Daniel,

Processing time > 2 * CPU time, this can be cause by a CPU bottleneck or a problem with communication between systems.

Also check if time consuming on RFC interface is large in same STAD screen.

You can use ST12 to trace this transaction performance as per .

Regards,

Ning

[former_member201054]

Hi Ning and Henry..

Thanks for the replies. what about the database response time..Is it within limit?

so the response time should be always below standard value ?

Average response time :1000 ms

Average CPU time : 400 ms

Average wait time : 10 ms

Average load time : 100 ms

Average database time per dialog step : 400 ms

Thanks in advance

[former_member201054]

Hi Experts,

Need answers for above post... Please guide and clarify.

Thanks in advance

[former_member182967]

Hi Daniel,

so the response time should be always below standard value ?

In my view, they are general permanence metrics.

Not always apply to all cases.

Currently, it is necessary to find and fix the high processing time problem firstly.

Regards,

Ning

[former_member201054]

We are calculating the response time based on the threshold value.

I read somewhere that processing is almost equal to response time.

In our case, I want to understand how we are concluding that processing time is high and other response times are quite normal. Please explain.

Thanks in advance

[former_member201054]

Hi,

Please help me for the comparison between response time captured from system and standard threshold value..I am bit unclear with it.

I will appreciate all your inputs and guidance

Thanks in advance

[Former Member]

Hi Daniel;

I saw your screen from STAD transaction, I can observe a high processing time related to the time of execution of the process, however, if you want to get more detail, you can trace the process with ST05, ST01, SAT, transactions etc.

Regards.

Henry Orellana