1 nih era database resource plan last updated: 6/19/2003 by era operations for techrep meeting...
TRANSCRIPT
1
NIH eRADatabase ResourcePlan
Last Updated: 6/19/2003
by eRA Operations
for Techrep Meeting
“Doing more with less”
2
Agenda
Vision for eRA Systems
Goals
Summary of Planned Changes
High-Level Plan for Dependable Performance
Benefits
3
Vision Statement
The vision is to have a highly available, secure, responsive, and centralized On Line Transaction Processing (OLTP) and Reporting environment that supports all internal and external user requirements
4
Goals Not Goals
Identify problem areas for tuning
Prevent runaway processes from affecting users
Help move long running jobs to off hours
Break applications
Break extension systems
Prevent users from getting information they need
Bottom Line: Implementation to Productiononly after mitigating application and user risks
5
Summary of ChangesResource plans set priority for processing if there is contention for CPU Online_group (users)
Commons 50% Internal IMPAC 35%
Batch_group (link accounts, bridge) 10% Other 5% - users not in any group
Limits reduced for CPU per statement User limit reduced from 13 to 3 minutes Link limit reduced from unlimited to 13 minutes (more considered
for off hours)
Idle time reduced from 4 hrs to 2 hrsDisk reads per statement User limit set to 8Mb Link limit set to 24Mb
6
High-level Plan for Dependable Performance
Alert extension system owners of plans and ensure they plan to port their applications to IMPSTG after it is refreshed 7/11/03Set new profile limits and resource plans in Test and Stage after July acceptance testing is completed 7/21Testers regression test application ~ 3-4 wks Identify problem areas and either tune application or increase limits
Have ICs test in IMPSTG Tune their extension system interface Keep IMPSTG open for IC development/testing If LINK accounts need more resources, consider allowing larger
limits off hours (8pm to 8AM)
After testing and approval by Link users/Testers, deploy config changes to prod (Target 8/31/03)
7
Benefits
More consistent and improved performance for all users and applications
Identify problem areas in the applications, extension systems, bridges, or batch jobs
Save $$$ - do more with less Support more load without adding significant new
technical infrastructure These recommendations are a best practice for
enterprise systems
8
End of Presentation