Monday, April 28, 2008

Tips:2 Performance analyis

st22
If a lot of shurtdumps are written in one day, that could be a hint, that there are general problems, which also causes the performance problems.
- Check shortdumps

sm21:
The syslog could also contain some information, which could be helpful, if you are looking for performance problems. Check the syslog for warnings or errors. This could be done with transaction sm21.
- Check syslog

st02
Check the buffer and the memory consumption. You can also check, if buffers are too small (swaps) and the hit ratio. If there are a lot of swaps, it could be helpful, to raise the affected buffer. If you double click on a buffer you will get more detailed information about this buffer. If you just mark it and click on current parameters, you will get a list of all parameters, which influence this buffer.
Another important part of the transaction is the table, which gives an overview about the SAP Memory. You can check, how much memory (extended memory) is allocated. How much is used. If heap memory (private memory which is used by one dedicated user) is allocated, you can see how much is allocated. If you double click on one of these entries and then choose the button “mode list” you will get a list of all modes, which are currently opened. With this screen you can find out, which mode is using heap memory or is using a high amount of extended memory.
- Check swaps of the buffers
- Check hit ratio of the buffers
- Check allocated and used memory
- Check if heap memory is used.
- Check the mode list to find modes, which uses a lot of memory

st04 (only for MSSQL)
If the system is running on a MSSQL database, you could check the buffer of the database, and the hit ratio of these. Often performance problems occur, because the memory is not fixed. If this was not configured, especially MSSQL 2005 will take as much physical memory as possible.
- Check if the memory of the MSSQL server is fixed
- Check the size of the database buffer (1/3 of the physical memory, if only one system is running on the server)

No comments: