Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Highlevel _ PS Performance Tuning Approach

Highlevel _ PS Performance Tuning Approach

Ratings: (0)|Views: 18|Likes:
Published by Nevin Prasannan
High level approach for Peoplesoft performance tuning
High level approach for Peoplesoft performance tuning

More info:

Published by: Nevin Prasannan on Aug 12, 2012
Copyright:Attribution Non-commercial


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





PS performance tuning approach1. Introduction:It is a widely known fact that 80% of performance problems are a direct result of the poorperformance, such as server configuration, resource contention. Assuming you have tuned yourservers and followed the guidelines for your database server, application server, and web server,most of your performance problems can be addressed by tuning the PeopleSoft Application.This article 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 notapply to your environment.2. Server Performance: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 on an individualcomponent 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 resources needed toserve the end-users.Traditional tools used to measure utilizations impact the system being measured and ultimatelythe end-user experience. Commands like the following provide snapshot data but not without anassociated cost. These tools can consume a significant amount of resources so care should betaken when executing 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 theserver. Is the problem in the CPU, I/O or memory? These native tools provide indicators, but at
the same time could skew the results because of the overhead associated with them. Typically,additional third party tools are needed to complete the analysis.The last hurdle being faced in tuning the server is making timing decisions on when to upgradethe hardware itself. To do this, much more information needs to be collected and stored in orderto understand if an historical spike in resource utilization was a one-time aberration or a regularoccurrence building over time. The recommendation is to look at third party vendors forsolutions 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.3. Web Server Performance:The release of PeopleSoft Pure Internet Architecture(TM) 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-userrequests 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 web servers:o Ensure load balancing strategy is soundo Implement a solution to verify and highlight changes in traffic volumeso Closely monitor the response times to verify that the strategy is optimizing the web serverso Measure and review historical patterns on server resource utilization (see server section above).o Increase the HEAP size to 200, 250, 300, or 380 MB for the web logic startup script.4. Tuxedo Performance Management:Tuxedo is additional middleware PeopleSoft utilizes to manage the following Internetapplication server services:o Component Processor--Responsible for executing PeopleSoft Components--the corePeopleSoft application business logico Business Interlink Processor-- Responsible for managing the interactions with third-partysystemso Application Messaging Processor--Manages messages in a PeopleSoft system
o 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 applicationo Security Manager--Authenticates end-users and manages their system access privilegeso Query Processor--Executes queries using the PeopleSoft Query toolo Application Engine--Executes PeopleSoft Application Engine processeso Process Scheduler--Executes reports and batch processes and registers the reports in thePortal's Content Registryo 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 to capture when analyzing tuxedo are:o Transaction volumes by domain, server, and applicationo Response time for each end-user requesto Tuxedo service generating a poor performing SQL statemento Break down of Tuxedo time by Service time and Queue timeo Identify problem origin - is it in tuxedo or the database?o Response time comparisons for multiple Tuxedo ServerReports has shown that too often companies throw hardware at a Tuxedo performance problemwhen a more effective solution can be as simple as adding another domain to the existingserver(s). This is due to the fact that PeopleSoft and Tuxedo lack management solutions thatprovide historical views of performance.5. Application 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 database environment:o Make sure the database is sized and configured correctlyo Make sure that the hardware and O/S environments are set up correctly

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)//-->