Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Performance tuning.pdf

Performance tuning.pdf

Ratings: (0)|Views: 8 |Likes:
Published by rmalhotra86

More info:

Published by: rmalhotra86 on Sep 17, 2013
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





It is a widely known fact that 80% of performance problems are a direct result of the to poorperformance, such as server configuration, resource contention. Assuming you have tuned yourservers and followed the guidelines for your database server, application server, and webserver, most of your performance problems can be addressed by tuning the PeopleSoftApplication.
This paper presents methodologies and techniques for optimizing the performance of PeopleSoftapplications. The methodologies that are discussed are intended to provide useful tips that willhelp to better tune your PeopleSoft applications. These tips focus on tuning several differentaspects within a PeopleSoft environment ranging from servers to indexes. You will find some of these tips provide you with a significant improvement in performance while others may not applyto your environment.
In general, the approach to application tuning starts by examining the consumption of resources. The entire system needs to be monitored to analyze resource consumption onan individual component basis and as a whole.The key to tuning servers in a PeopleSoft environment is to implement a methodology toaccurately capture as much information as possible without utilizing critical resourcesneeded to serve the end-users.Traditional tools used to measure utilizations impact the system being measured andultimately the end-user experience. Commands like the following provide snapshot data butnot without an associated cost. These tools can consume a significant amount of resourcesso care should be taken when you execute them.a) df sizeb) iostat swapinfoc) ipcs timexd) netstat topf) ps uptimeg) sar vmstath) swapinfo also glance & gpmThe goal of using these native commands is to identify, if and where, a bottleneck is in the server.Is the problem in the CPU, I/O or memory? These native tools provide indicators, but at the sametime could skew the results because of the overhead associated with them. Typically, additionalthird party tools are needed to complete the analysis.
The last hurdle companies are facing in tuning the server is making timing decisions on when toupgrade the hardware itself. To do this, much more information needs to be collected and storedin order to understand if an historical spike in resource utilization was a one-time aberration or aregular occurrence building over time. The recommendation is to look at third party vendors for solutions that can collect key performance indicators while minimizing overhead on the system.The collected data can then be put in a repository for detailed historical analysis.
The release of PeopleSoft Pure Internet Architecture™ introduces new components toPeopleSoft architecture—the web server and application server. The application server is wheremost shops struggle with appropriate sizing. Web servers are used for handling the end-user srequests from a web browser to eliminate the administrative costs associated with loadingsoftware (fat clients) on individual desktops. The benefit is a significant savings on softwaredeployment costs, maintenance, and upgrades. While the shift from fat clients to thin lessens theadministrative burden, it increases the need to ensure the web servers are finely tuned since theywill service a large number of clients. The requirement for these web servers to achieve optimalperformance is vital due to the mission critical-nature PeopleSoft plays in today’s enterprise.Recommendations for ensuring good performance for your web servers:
Ensure your load balancing strategy is sound
Implement a solution to verify and highlight changes in traffic volumes
Closely monitor the response times to verify that your strategy is optimizing your webservers
Measure and review historical patterns on server resource utilization (see server sectionabove).
Increase the HEAP size to 200, 250, 300, or 380 MB for the web logic startup script.
Tuxedo is additional middleware PeopleSoft utilizes to manage the following Internet applicationserver services:
Component Processor 
—Responsible for executing PeopleSoft Components—the corePeopleSoft application business logic
Business Interlink Processor 
— Responsible for managing the interactions with third-partysystems
 Application Messaging Processo
—Manages messages in a PeopleSoft system
User Interface Generator 
—Generates the user interface based on the Component or Querydefinition and generates the appropriate markup language (HTML, WML, or XML) and scriptinglanguage (JavaScript, WMLScript) based on the client accessing the application
Security Manager 
—Authenticates end-users and manages their system access privileges
Query Processor 
—Executes queries using the PeopleSoft Query tool
 Application Engine
—Executes PeopleSoft Application Engine processes
Process Scheduler 
—Executes reports and batch processes and registers the reports in thePortal’s Content Registry
SQL Access Manager 
—Manages all interaction with the relational DBMS via SQLThis Tuxedo middle tier is another critical and influential component of performance. Similar tothe web server, what is needed is a way to see into the “black box” to further understand some of the key performance metrics.
 Some of the performance metrics you want to capture when analyzing tuxedo are:
Transaction volumes by domain, server, and application
Response time for each end-user request
Tuxedo service generating a poor performing SQL statement
Break down of Tuxedo time by Service time and Queue time
Identify problem origin – is it in tuxedo or the database?
Response time comparisons for multiple Tuxedo Server Our experience has shown that too often companies throw hardware at a Tuxedo performanceproblem when a more effective solution can be as simple as adding another domain to theexisting server(s). This is due to the fact that PeopleSoft and Tuxedo lack management solutionsthat provide historical views of performance.
It is an accepted fact that 80% of application and database problems reside in the applicationcode. But, there are other technical items to consider which could influence the applicationsperformance. Here are some specific items to focus on when evaluating your databaseenvironment:
Make sure the database is sized and configured correctly
Make sure that the hardware and O/S environments are set up correctly
Verify that patch levels are current
Fix common SQL errors
Review documentation of known problems with PeopleSoft supplied code
Be sure to check available patches from PeopleSoft that might address the problem
Review PeopleSoft suggested kernel parameters
Set up the right number of processes
Review the application server blocking for Long Running Queries
Make sure you don’t undersize your version 8 application server It is also recommended to continue to review these items on a periodic basis.
The performance of an application depends on many factors. We will start with the overall generalapproach to tuning SQL statements. We will then move to such areas as indexes, performancemonitoring, queries, the Tempdb (Tempdb is often referred to as plain “TEMP”), and, finally,servers and memory allocation.To understand the effect of tuning, we must compare ‘time in Oracle’ with ‘request wait time’.Request wait time is the time that a session is connected to Oracle, but not issuing SQLstatements. In Oracle time shows the amount of time resolving a SQL statement once it has beensubmitted to Oracle for execution. If time in Oracle is not significantly smaller than the requestwait time, then application tuning should be examined. Request wait time is almost always muchgreater than in Oracle time, especially for on line users, because of think time.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->