This set of posts covers a set of common Linux commands that you can use to do initial troubleshooting when the SOA Suite environment is up and running, but very slow.
Identify bottleneck area
Basic process is such that:
- First identify if the problem is on the CPU side or on the IO side
- If it is on the CPU side, identify the process that is eating the memory or if there are too many processes in the system (system is over capacity)
- If it is on the IO side, identify if the system is trashing (all processes combined use more main memory than available in the system) or if some process is eating all IO capacity, then identify the process eating IO
- For database, find out if some SQL query is not using indexes correctly. There is a number of guidelines from Oracle to do these (not covered here, please move along...)
- For advanced trouble shooting EM and diagnostics packs or statistics packs can be used (not covered here)
In the process of troubleshooting you may do configuration or other changes to the system. In order to understand what is the root cause for the problem (you will need to build an understanding of this or the problems are bound to re-appear again and again), it is important you change only one parameter at a time is changed and then you monitor the system again (or re-run your performance tests if you are have a replica of production system available). This is a way to see how each parameter affects the performance.
Ei kommentteja:
Lähetä kommentti