cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Performance issues

Former Member
0 Likes
9,225

Hi all,

I need some pointers as to how I can narrow down users' complain of poor response time/performance whenever they run a transaction.

I understand that there are many considerations e.g. PC specs/speed, network, etc that will affect users' performance but at least as far as the SAP servers are concerned, where the bottlenecks/choke points are.

From ST06, the paging is good as most of the hour-to-hour stats showed 0 or below the 100 range. This should mean that there are enough physical memory and is not a memory issue, right?

Is this the only stats I should be looking at?

Would anyone be able to advise on what are the steps that I should follow at least to say that the performance issue is not at the SAP end?

Thanks

View Entire Topic
Former Member
0 Likes

If i get a complain from end user for poor performance of system.. i try to drill down like this :

Check ST03N : here first i try to find out transaction user is executing and are taking more time(most of the time complete system is not slow ..only a few transaction is slow). After this i check what component of that transaction is high.. DB time or GUI time or wait time..

for example : high db time points towards expansive SQLs and high wait time towards possible unavailability of workprocess.

Also, i know if this is a Z* transaction or standard one.. so now i have to work with SAP note or ABAP person.

many times, for Z* transactions, we get expansive SQL easily with ST04 transaction which can be tuned by ABAPer with creating new Indexes.

Also, few time just rebuilding indexes & stats run for table help.

thanks

ashish