sap i/o performance related jobs - st04

[Former Member]

Hi ,

In general SAP system will have N number of  running jobs, but i would like to identify the I/O JOBS running at any particular time.

Is there any program or any other methods available to point out the I/O jobs in an SAP system.

Regards,

Prakaash 

[Former Member]

Hi Prakaash,

Use STAD transcation for uch memory and I/O issues, This will help you.

Take this report for 2 days 24hrs and then analysis. Default time duration for STAD is 10 mins, Hence it will slow or will not repond, then split it to 6hrs * 4 may work . This is based on your memory and Hardware config.

Thanks,

Prabhakar

[Former Member]

Hi Prakaash,

Check in ST03N for Top Dialog  and Background Response Time & Database Time .Check for there DB Time also.This will help you to identify which job is causing more DB Time and help for your performance issue

Thanks & regards

Amit

[JPReyes]

to identify the I/O JOBS

I don't understand what do you mean with I/O?... 

[Former Member]

Hi Juan,

In specific, the system is taking high number of input /output (i/o) and we are having big performance problem in the server. With the help of OS / DB specialist, we are addressing it out one by one. However in ST04 we could notice that, number of i/o is getting high and we are not sure about which job or process or activity is causing that.

In order to identify the root cause of high i/o in the system - What I have to do from SAP perspective and that will help me to narrow down the problem (For instance, if the i/o because of frequent jobs - I will check with the team to reduce the frequency or necessity of it or if the i/o because of high SQL query then I will be ask our ABAPER to fine tune the programs)

Hope I am clear with it, if not please let me know.

Thanks and  Regards

Prakaash

[JPReyes]

Well, you could do an SQL trace on the jobs and analyze the statements to see which ones are expensive statements and if they are using the indexes in the right way.

I'll be keeping an eye specially on jobs that cause excessive amount of sequential readings as this is most likely an issue with bad indexes that can be easily corrected.

Regards, Juan