One of the main recurring complaints from PeopleSoft users is decreased or degraded performance over time. Users often judge performance based on their own experience with the system and in terms of the tasks they often execute within that system. Their perception of good/bad performance might be different than yours. However, as system administrators, our challenge is to put in place some proactive steps to provide a smooth experience for our PeopleSoft system users. In this blog, I want to share with you some of the tips we have implemented with different clients that have yielded improved system performance:
– Reconfigure Application / Process Scheduler servers periodically. Your initial configurations worked well for a certain period of time. But, as more functionality is added and more processes are running within the system, it is important to revisit the minimum and maximum values of server processes within the configuration files and adjust them accordingly.
– Turn off Traces. Traces are meant to help developers troubleshoot and trace program / system errors in development and test environments. But, sometimes, developers have to trace in a production environment to address an urgent program error. If these traces are ‘accidently’ left on, they can negatively impact system performance.
– Schedule PeopleSoft processes carefully and ‘wisely’. Having too many jobs, especially long running ones, scheduled to run during peak times can create heavy traffic within the system. For example, at one of our clients, we scheduled most of PeopleSoft processes to run after business hours and overnight to improve run time and traffic load.
– Configure Integration Broker properly. If you operate in a load balanced environment, it is important to use domain failover to process messages and service operations. Make sure that a service operation is handled by one and only one service domain.
– Archive Data. Your database is probably storing years of data. It is beneficial to archive old data according to your company retention policy. For example, at one of our clients, we archive all Time and Labor data that is older than six months. As a result, many of PeopleSoft processes that use Time and Labor data run quicker, which frees more system resources for the users.
– Gather statistics periodically. Make a habit to update statistics of PeopleSoft tables and indexes. Oracle often recommends regenerating statistics for only non-temporary tables and indexes (refer to Doc ID 747254.1 on Oracle Support website). Updated statistics can positively impact query performance within your database.
– Rebuild indexes. As it is the case with updating statistics, rebuilding indexes is also beneficial in eliminating index fragmentation and repairing blocks that are affected by frequent insert/delete/update statements.
I hope these tips get you started on the right path when tackling PeopleSoft performance issues. Please share your own tips and experiences dealing with performance issues. If you have any questions, please feel free to post it here.