Posted by Coder.
Oct
3
Posted by Coder.
Attributes of a Scalable (data intensive) Application
Cary Millsap, former VP of Oracle’s System Performance Group and the cofounder of Hotsos.
…doing things an application doesn’t need to do is exactly what makes it slow, unscalable, and—in the end—economically inefficient.
- Don’t run reports that nobody reads.
- Don’t generate more output than you need.
- Don’t execute a business process any more often than the business needs.
- Don’t write SQL that visits more blocks in the database buffer cache than necessary.
- Don’t update a column’s value to the same value it already has.
- Push data when it’s ready instead of forcing applications to poll to see if there’s any work to do.
- Don’t generate redo and undo when you don’t need the recoverability benefits provided by generating it.
- Don’t parse any SQL statement that you could have pre-parsed and shared.
- Don’t process DML one row at a time; use array fetches, bulk inserts, etc.
- Don’t lock data any more often or for any longer than is absolutely necessary.
While I won’t pretend that the list is complete, I do believe that it should help you get into the spirit of understanding what an appropriately lean application should look like.
Technorati Tags: Oracle
There are 0 comments to this post.
Add Your Comment.
Previous Post
« JouleSort and SPEC Power: Benchmarks for evaluating energy efficiency Next Post
Scalability chez Wall Street vs. chez Web2.0s »
« JouleSort and SPEC Power: Benchmarks for evaluating energy efficiency Next Post
Scalability chez Wall Street vs. chez Web2.0s »