Ansicht
Dokumentation
01183 - Average response times
Addresses (Business Address Services) Vendor Master (General Section)This documentation is copyright by SAP AG.
Average response times
Ubiria,I did not notice whether you qualified the response times to be just for DIA?
You would want to make sure to do that.
If users are running reports "online" vs. submitting to batch; this could impact
your response time numbers. When we first went live, this happened to us.
Little things like making sure that the users do not have access to SE38 / SA38
& training, training on the "submit to batch" functionality
There are many indexes which we have built in response to poor performance; SAP
does not ship many as this would be too much overhead.
Also, tables which are shipped with buffering turned on & have become too large
to buffer causes performance issues therefore requiring the buffering to be
"turned off" on the table.
Custom ABAP has been our biggest problem. If the programmer does not run a SQL
trace over their code; there are times when the code is not doing what the
programmer expected.
I would pick one of your most frequently used transactions & work with a user to
perform ST05 traces over the transaction.
Look at the trace. Is the same record in a table being read multiple times? Is
a single select statement taking more that a subsecond.
Hope this adds some info too
Doreen
-----Original Message-----
From: Mike Martin, IS, Sousa [mailto:MMartinZs...]
Sent: Thursday, March 01, 2001 12:21 PM
To: 'Ubiria, Fernando'; Foro SAP AS/400
Subject: RE: Average response times
Ubiria,
I would suggest looking at the average response times per transaction, not per
hour. The figures you sent can be very deceiving. For example, if you run SM50
every 2 seconds, for an entire hour, you will probably cut your reported
response times in half for that hour. Obviously, you are not attempting to
purposefully skew the results, but this is inherent in SAP. Your users will
perform many transactions heavily during certain periods of the day (for us, all
PGI occurs late in afternoon, for example).
Because of this, I believe that none of the aggregate figures are extremely
useful unless you view them per Tcode or program. Even then you have to be
careful. For example, VA01 may report times of 1500ms on average when on one
day it jumps to 3000ms. This perceived degradation in performance could be
attributed to many factors (normal orders are approximately 5 lines, on the bad
day a few orders came in with thousands of lines, etc.).
If you do an analysis by Tcode, you might find that only a handful of programs
are experiencing 'unacceptable response times'. There may be specific OSS
notes, recommended secondary indices, etc, for each offending
transaction/program. If, however, you find that all response times are
unacceptable for all programs/tcodes, then perhaps you have to analyze system
configuration, hardware, etc.
Regards,
Mike D. Martin<?xml:namespace prefix = o ns =
"urn:schemas-microsoft-com:office:office" />
SAP Basis Administrator
SOLA Optical, USA
707-763-9911 x6106
mmartinZs...
-----Original Message-----
From: Ubiria, Fernando [mailto:fubiriaZg...]
Sent: Thursday, March 01, 2001 3:09 AM
To: Foro SAP AS/400
Subject: Average response times
Hello again,
I've received the table in the mail in a way very difficult to read. I hope this
one is better.
Jan 2001
Feb 2001
Week 7 2001
Week 8 2001
2001.02.26
2001.02.27
2001.02.28
08-09
1.209
1.415
1.513
1.725
1.443
741
1.410
09-10
1.403
1.663
1.913
1.602
1.272
927
1.061
10-11
1.410
1.391
1.887
1.195
1.430
1.387
1.024
11-12
1.255
1.353
2.009
876
1.825
566
828
12-13
1.116
1.464
1.999
984
1.220
917
737
13-14
1.036
1.500
1.781
825
1.294
1.086
1.616
14-15
857
670
573
1.023
536
290
1.227
15-16
1.208
1.040
1.236
992
673
639
1.482
16-17
885
928
943
1.053
646
490
1.051
17-18
987
988
1.077
1.308
1.171
475
611
Regards,
Fernando Ubiria
Durban Tours - Südafrika Safari
ROGBILLS - Synchronize billing plans TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 5445 Date: 20240603 Time: 102414 sap01-206 ( 3 ms )
