Performance Monitoring Tools Vmstat

Oracle Performance Tuning: Always Follow A Systematic Approach

Even with PeopleSoft, there is a possibility that issues pertaining to performance might crop up which would actively hit the performance of the entire application. There are lot many imperative factors that play a vital role in Oracle performance tuning such as load balancers, network, system hardware, network and SAN’s. Each of these components has individual tuning parameters and if any of these are not tuned appropriately, one can end up with a poorly performing application.

One big sigh of relief in the case of PeopleSoft load testing is that the entire process is not going to take much time and is not much expensive also. Before anyone starts with the oracle performance tuning process, one needs to come out with a complete plan that involves which performance tuning tool is to be used which data has to be captured. The performance tuning plan should provide a complete framework and the efforts that would go in the PeopleSoft Load Testing process.  A precise and result driven plan is the one that incorporates decisions like what tests need to be conducted, what is to be measured and how to determine that the results are satisfactory.

]]>

When one plans to write the performance testing scripts, it is to be assured that the scripts for each and every component are not written. The most common on track activities are the ones that have to be included. One more thing, the worst case scenarios are never to be included in the PeopleSoft load testing process. Oracle performance tuning involves carefully choosing a performance testing tool that would in its peak state would not generate transactions more that the number common on the busy days.

Most of the PeopleSoft benchmark reports define a concurrent user, just as someone who enters one transaction every 3 minutes. Assembling the Oracle performance testing team holds vital importance as with this one will find out the individuals that have already performed well in that concerned area. At this stage, one needs to find a DBA to monitor the database, a System administrator to monitor the OS and a network engineer to monitor the network.

Capturing the performance is not as tough as many might percept it to be. Windows provides a way to capture performance data and on the other hand while running on UNIX it is quite easy to redirect VMSTAT. Some of the common observations that are to be performed on regular basis are:

If the performance issues crop again and again, then the disk IO might be the culprit.

Single indexing can fix the original perform in most of the cases, if not, then the Oracle performance expert needs to be engaged in the PeopleSoft load testing procedure.

Hardware based solutions do not most the times help deal with performance related issues.

The very first step to be followed for Oracle performance tuning is to normalize the application workload. Once this is done, the administrators can modify the physical implementation of the system. Reducing the contention bottlenecks is the final step to oracle performance tuning.