System Performance Slow

Basis (Basis Technology Modules: Basis Component/System Administration, GUIs)

Moderators: Snowy, thx4allthefish

Post Reply

System Performance Slow

Post by karunkumar » Tue Jun 03, 2003 2:22 am

SSAA-------Administrative Functions (Alert View)---Execute

Monitoring Performance : 1)SAP :Checking Performance System Workload
-System Load
-Response Time [2 Alerts] 3.042>3.000 msec Dialog response Time exceeds thresholds (629 dialog steps)
-Frontend Response Time [2 Alerts] 3.199 msec >3.000 msec Frontend response time exceeds threshold(629 dialog steps
-DBRequestTime[2 Alerts], 4.087 >3.000 msec dialog DB request time exceeds threshold [274 dialog steps]
-LongRunners[6 Alerts], Long Running Report SAPLSTXBS has been running 635 sec in dialog, Threshold:600 sec

2)SAP:Checking Performance - Buffer Performance
-Buffer Proformance
-SpaceUsed [1 Alerts] 99% > 98% 15 min. avg. value over threshold value
-Single Record
-Hit ratio [1 alert] 79%<80% 15 min. avg. value over threshold value
-Generic key
-Space Used [1 alert] 94% > 90% 15 min. avg. value over threshold value
-Space Used [2 Alerts] 99%>98% 15 min. avg. value over threshold value

can u plz tell me why the system performance is slow and how to rectify.
its a Development Server.

Revert back me ASAP
K Arun Kumar

Posts: 1760
Joined: Fri May 23, 2003 5:33 am

Post by SAP_Basis_Chap » Tue Jun 03, 2003 3:02 am

Hi there,

Not a simple question you ask here.

Dialog response time
On a not very busy system this will be high as by default Basis response times are high and only get reduced due to end users getting lower responses. I would use transaction STAT (STAD from 610) to check for all response time above 3000 ms at the time of the reported prob. You can then judge if they are end user of batch/basis which are probably not an issue. You can use ST03 to make a more historical look at the transaction(s) with bad response.

Frontend Response Time
There are notes out there that discuss that this is not a very good alert. I would personally ignore it and if users are complaining about bad performance then reviuew the network with NIPING initially.

Dialog DB request time
Could be an issue but needs to be reviwed via ST04. I have no idea on your DB so will not comment further.

Long Runners
10 minute jobs are certainly common nowadays. This also needs to be reviewed as to the data being read/written and the performance of such. Poor programming can be an issue here. You have stated a SAP program which could be checked via notes for issues, generally with SAP programs it is the data being read or the customizing structure being a little astray that cause this performance prob.

I would not worry at all about space used alerts and do not consider these an issue. A buffer with 100% used space can erform at 100% but a buffer at 90% used can perform at 10%. The hit ration is important.

Your generic buffer hit ratio is poor which can be due to a few problems like too many updates in a table too often, A table being too large or being generic rather than single, or ironically if the directory space is too small!. I would not alert on both hit ratio and %used as you will get 2 alerts for one problem (poor hit ratio).

being a dev server
I would concentrate on the prod server and spend all my time learing about performance rather than monitoring a dev server. I would wait for developers to complain. They are always hacking with tables and programs so buffers and response times are often poor by default.

Good Luck! :)

Posts: 553
Joined: Wed May 28, 2003 6:12 am
Location: !!!! Go COLTS !!!!

Post by nainesh » Tue Jun 03, 2003 3:22 am


Since this being a development server, u cannot lay a fixed baseline for as to what to tune..because they will be constantly updating/changing programs..customization etc...As a basis admin what u can do is to help them tune their programs by finding out the xpensive sql's and refining them..


Post Reply