Evaluating and Meeting SLAs - Performance Requirement Guidelines
By Paula Speranza-Hadley on Feb 27, 2014
Implementations typically need to establish performance goals that the system will need to meet. At times these goals come from RFPs or customer requirements in the form of Service Level Agreements (SLA). At Oracle, when establishing performance goals, we use a set of “default” performance requirements, and any change from that (higher or lower) is an exception, usually based on the weight or complexity of the transaction. Forms Validations and Posting is an example of an exception. The implementation team will have to be careful about applying the general rules to everything.
Our default performance requirements are:
- OLTP, 3 secs for an average weight transaction (for 90% of transactions) e.g.Post a Payment using Payment Event Quick Add
- OLTP, 5 secs for a above average weight transaction (for 90% of transactions) e.g. Post a Form
- Batch - 50K records per hour
Unless the transaction is a known or suspected exception (based on weight or complexity), partners could reasonably expect to meet these objectives in planning with good sizing, competent infrastructure planning, good testing, and quality configuration. These default goals could help flag items that need further examination.
While we cannot guarantee performance metrics because of the customer configuration involved, we are able to provide support if an implemeter encounters difficulties meeting SLAs.