High response time for a transaction

[Former Member]

Dear all,

I have in my production system a transaction that increased in the response time 645%.

I have the average time showing the increase, but I  need to know more exactly if the transaction executes normally and only once very long, or it always has a high response time.

In conclusion, I am not interested in the average time, but more to see how the response time exceeded to such a high value.

Is there any possibility to check that ?

Thanks in advance,

Jordan

[JPReyes · Accepted solution]

Absolutely... simple run a trace and you can analize the SQL statements to see where the problem is coming from.

The first thing I usually look into is that the indexes are set corretly, if you can see that the dialog process is taking a lot of time doing sequencial readings from the database this is a strong sign that the indexes are not fit for porpuse.

Regards, Juan

[Former Member · Accepted solution]

Hello Juan,

Thanks a lot for help.

How can I start a trace on some transaction ?

Thanks in advance,

Jordan

[JPReyes · Accepted solution]

Use transaction ST05.

Regards, Juan

[Former Member · Accepted solution]

Dear Juan,

Is there any possibility to check it in the past ?

I will activate tracing to check it, but I need to check it in the past as well ... to see why we had such a high RT.

Thank you,

J.

[Former Member · Accepted solution]

Hi Jordan

In st05 you can't able to get the past data,you can only see present execution information.And also please execute SE30(Abap Runtime Analysis) by doing this you can conclude that where the transaction is taking more time whether at db or cpu side.

Thanks

[Reagan]

Hello

Perform a runtime analysis of the Tx using the Tx SE30

http://scn.sap.com/community/abap/testing-and-troubleshooting/blog/2007/11/13/the-abap-runtime-trace...

Additionally you can run ST05 for tracing of the statements.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5a1de990-0201-0010-8d83-a06bdda1d...

By this way you can analyse the execution plan.

Check whether the optimizer is picking up the right indexes during the execution.

If there are indexes present and the system is not using the right indexes during the execution of the statement then update the statistics for the tables in the query.

If the problem is with a custom ABAP then you probably need to speak with the developer to optimize the code.

Good Luck

RB