CMS Performance
Ensuring that CMS applications perform to a high standard is an ongoing challenge. Resolution of periodic performance problems and optimizing the performance of current and future releases requires the cooperation and collaboration of all involved in the CMS service model: Providers (Unisys and PeopleSoft), Central CMS (infrastructure and applications), and campuses. Resolution of problems and success in defining performance metrics and conducting periodic performance measurement and analysis will require an organized approach and a concerted effort by all concerned.
Resolving current performance problems will begin by analyzing the CMS components common to all campuses: the Salt Lake City infrastructure and the CMS baseline releases. Specific campus performance issues can be addressed by campuses concurrently with baseline resolution efforts, however dedicating resources to performance analysis of common components first should provide the greatest benefit to the greatest number of users across the system. Focusing on shared resources will also benefit campuses in the long term by providing performance benchmarks for baseline releases that can be used by campuses to assess the performance of local modifications and configurations.
All documents are posted as Microsoft Word unless otherwise indicated.
Performance Management Documentation
- Application Performance Management Process
- PAT Communications Plan
- PAT Communications Strategy
- Performance Ticket Management Presentation (.ppt)
- Fresno Registration Review
Performance Ticket Analysis Reports
2008
2007
Measures & Tools
- Benchmarking with Oracle/PeopleSoft Ping (.ppt)
- Oracle Performance and Veritas i3 (.ppt)
- Peoplesoft Query Perfomance Tips
CMS Application Benchmarking Project
- Campus Application Timing Instructions
- Campus Application Timing Worksheet - Batch Processes
- Consolidated CMS Application Timings - Batch Processes
Performance Action Team Official Communications