http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/webcontent/uuid/925b02f9-0b01-0010-bbbf-c68268bb3c41" width="235"/> http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/webcontent/uuid/7ec202f9-0b01-0010-589e-a51bcd596fed" width="235"/> The NetWeaver platform is made up of several different components such as database processes, work processes, memory buffers, table structure and data, hardware parts like the CPU, main memory, disk drives and network. All these pieces work smoothly and interact together. If for any reason one of them fails or reaches its maximum performance boundaries, the overall health of the entire system will then be compromised and response time performance will drastically be affected in a negative way. We can define three major groups within performance analysis and tuning: 1. Technical layer group. 2. Application layer group. 3. Hardware layer group. 1) The Technical layer focuses mostly on analyzing and optimizing performance in the database interface, index definition and creation, core NetWeaver components like work process distribution, memory area sizing and table buffering. In this group, you will need to perform a thorough workload analysis and then change and/or enhance the system settings to accomplish positive performance results. 2) The Application layer is directly related to the program code. Unnecessary database calls, inefficient program design and poor use of available programs are the root cause of performance bottlenecks in a system. In this group, you will need to individually detect and correct the reason why it is currently impacting response times by analyzing the program code itself and fixing it accordingly. 3) In the Hardware layer, components like disk drives, CPU, network and main memory are key factors that will play a critical role in terms of performance. In this group, the hardware will be analyzed for bottlenecks to see if any of the above components has reached its limits and is negatively affecting the overall response times of your NetWeaver component; for example, if there is a hot spot in a database due to a slow disk drive. Along this journey you will learn to use the ASV method, a three step performance optimization approach, which goes as follows: - Analyze the problem: When dealing with performance issues always perform an initial analysis to determine at which of the component levels one of the interacting pieces is causing the bottleneck. Making a change to a system component such as to the software itself or even to the hardware without prior analysis is absolutely not recommended at all. - Small change: During the initial analysis you can find several different components in which enhancements can be performed. Always use caution and take only one step at a time. Never perform more than one change at once. You will otherwise never know exactly which one is successful or even which is the one that could cause undesired results. - Verify the results: After every change, always perform a new analysis to verify whether or not the enhancement has provided those desired results you were looking for. This is a cyclic redundant process. When one performance bottleneck is cleared a new one is just arriving to the table and you will need to start another ASV process again. That will keep you busy and happy for some time. Welcome to the journey!!!