This action might not be possible to undo. Are you sure you want to continue?
Course Structure Continuous Assessment: 50% ± Assignments: 25% ± Lab Sessions: 25% Lecturers: ± Prof. Ooi Beng Chin (ooibc) ± DBAs: Sze Eng Koon and Phillip Lim 2 .
3 . Jim Gray (ed): The Benchmark handbook : for database and transaction processing systems. Prentice Hall. Kaufmann Publishers. Kostelac: Oracle Performance Tuning 101. J.Text/Reference Books: Dennis Shasha and Phillipe Bonnet: Database Tuning : Principles Experiments and Troubleshooting Techniques.The Complete Book. Deshpande and J. REFERENCE. 3rd edition. 2002 (released in June 2002). REFERENCE (a good reference if cannot get the text book) Database Management Systems. Hector Garcia-Molina. M. Dennis Shasha: Database tuning : a principled approach. Vaidyanatha. 2001. 1991. Ullman. 1992. REFERENCE. Raghu Ramakrishnan & Johannes Gehrke. 2002. Osborne/Mc-Graw-Hill. and Jennifer Widom: Database Systems -. G. TEXT. 2001. McGraw-Hill. Jeffrey D. K. Prentice Hall. Morgan Kaufmann Publishers.
Copyright: Many slides belong to the tutorial: Database Tuning Principles. Experiments and Troubleshooting Techniques Dennis Shasha (email@example.com) And lecture notes provided by Database Management Systems. 3rd edition. and some from the web « 4 . 2002.edu) Philippe Bonnet (bonnet@diku. Raghu Ramakrishnan & Johannes Gehrke McGraw-Hill.nyu.
5 . though it may mean lower response time for time-critical applications. ³More quickly´ usually means higher throughput.Database Tuning Database Tuning is the activity of making a database application run more quickly.
Tuner Operating System Hardware [Processor(s). Memory] 6 . Data architect) Application Sophisticated Application Programmer (e..g.g..Application Programmer (e. business analyst. SAP admin) Query Processor Indexes Concurrency Control Storage Subsystem Recovery DBA. Disk(s).
Goals of the Course Appreciation of DBMS architecture Study the effect of various components on the performance of the systems Tuning principles Troubleshooting techniques for chasing down performance problems Hands-on experience in Tuning 7 .
5. 6. 4. Basic Principles Tuning the guts Indexes Relational Systems Application Interface E-commerce Applications Data warehouse Applications Distributed Applications Troubleshooting 8 . 8. 7. 3.Contents 1. 9. 2.
fix locally ± Localizing the problems Partitioning breaks bottlenecks (temporal and spatial) ± ONE part of the system limits the the overall performance ± Two approaches: Fix locally Partitioning the LOAD ± eg.Tuning Principles Think globally. Free list. lock contention due to long transactions Partitioning in space/logical resources/time9 .
running costs are low ± Start-up costs include Disk access Data transfer Query processing System calls ± Reduce the number of start-ups 10 .Tuning Principles Start-up costs are high.
11 Rule of Thumb Ex:1 KB Block .An example: Time = Seek Time + Rotational Delay + Transfer Time + Other Random I/O: Expensive Sequential I/O: Much less » Random I/O: b 20 ms. » Sequential I/O: b 1 ms.
Tuning Principles Render onto server what is due onto Server ± Task allocation between the server and the application programs ± Factors: Relative computing resources of client. application servers and data server ± Should checking be done in the middle tier? Location of information The nature of tasks: interaction with screen? 12 .
Indices 13 .Tuning Principles Be prepared for trade-offs Ex.
Tuning Mindset 1. Measure and document current performance 8. I/O. 2. 3. 4. Track and exercise change-control procedures 7. Set reasonable performance tuning goals Measure and document current performance Identify current system performance bottleneck Identify current OS bottleneck Tune the required components eg: application. OS etc 6. 5. Repeat step 3 through 7 until the goal is met 14 . contention. DB.