1. Summer 2018 Technical Updates
What changed this year?
Summer 2018 Results
Planned Work for
Considerations Beyond 2019

2. What Changed This Year? ODS PEIMS Database
Overall, performance was better than last year (2017) – but not good enough
ODS
PEIMS
Database
Updated servers from WIN2008 to WIN2012
Improved interchange processing (Disc & EdOrg) Implemented more targeted deletes
Resolved WebSeal errors when accessing Delete Utility (part Portal issue, part database issue)
Refactored PEIMS promotions and validations to allow for faster processing
Moved subset of validations from DROOLS to stored procedure (faster processing)
Performance testing to identify and troubleshoot long running jobs
After hours monitoring
Upgraded Exadata Server hardware
Increased tablespace to allow for deletes
Increased from 2 nodes to 3 nodes to allow added baselines to long running jobs – allowing system to pick the fastest execution plan
Monitoring all jobs processing longer than 10 min

3. Summer 2018 Results ODS PEIMS Data Mart Complete Add Batch Promote
Del Utility
Validate
Accept
Add Batch: 6 out of 8 ETL servers underperformed after OS Upgrade
Delete Utility: “Individual” deletes taking longer than “All Delete”
Promote: Basic Attendance , Course Completion, and Staff Basic processing outside our benchmark of 2 hrs
Validate: Basic Attendance, Course Completion, and Enrollment processing outside our benchmark of 2 hrs
Complete: stays on ‘95%’ during final calculations

4. Planned Work 2018-2019 ODS Planned Work PEIMS Planned Work
Remediate inconsistencies in ETL server performance after upgrade from WIN2008 to WIN2012
Remediate long running Individual deletes
PEIMS Planned Work
Continue fine tuning stored procedures performance for promotions and validations
Move remaining validations from DROOLS to stored procedures (faster processing)
Complete report conversion from BOBI to stored procedure based reports
Database Planned Work
Increase from 96 cores to 132 cores to better handle peak submission times
Continue working with Oracle specialist to address inconsistencies with performance

5. Considerations Beyond 2019
TSDS architecture was developed in 2009
Looking to take advantage of technological efficiencies:
Leveraging more efficient ODS solutions
Integration with SIS applications
Investigate cloud solutions
Facilitate elastic scaling
Cost effective to bring test and production environments in synch
Streamline business processes