Oracle 10g Performance: chapter 00 intro live_short
Download as PPT, PDF3 likes808 views
1. The document discusses Oracle performance tuning and provides biographical information about Kyle Hailey, an expert in Oracle performance tuning. 2. It emphasizes the importance of using visualizations and graphics to understand performance issues rather than textual data. Various graphs and visualizations of performance metrics are presented. 3. Troubleshooting steps are outlined that involve using tools like ASH, AAS, and OEM to identify issues related to the machine, database, waits, or SQL statements.
Ad
More Related Content
What's hot (20)
Viewers also liked (20)
Ad
Similar to Oracle 10g Performance: chapter 00 intro live_short (20)
Ad
More from Kyle Hailey (20)
![Oracle Open World 2014: Lies, Damned Lies, and I/O Statistics [ CON3671]](https://cdn.slidesharecdn.com/ss_thumbnails/thursday115ionfs-141107125307-conversion-gate02-thumbnail.jpg?width=560&fit=bounds)
Recently uploaded (20)
Oracle 10g Performance: chapter 00 intro live_short
- 1. Oracle Performance Tuning Kyle Hailey [email protected] dboptimizer.com
- 2. Who is Kyle Hailey ï§ 1990 Oracle ï§ 90 support ï§ 92 Ported v6 ï§ 93 France ï§ 95 Benchmarking ï§ 98 ST Real World Performance ï§ 2000 Dot.Com ï§ 2001 Quest ï§ 2002 Oracle OEM 10g Success!Success! First successful OEM designFirst successful OEM design
- 3. Who is Kyle Hailey ï§ 1990 Oracle ï§ 90 support ï§ 92 Ported v6 ï§ 93 France ï§ 95 Benchmarking ï§ 98 ST Real World Performance ï§ 2000 Dot.Com ï§ 2001 Quest ï§ 2002 Oracle OEM 10g ï§ 2005 Embarcadero ï§ DB Optimizer
- 4. Who is Kyle Hailey ï§ 1990 Oracle ï§ 90 support ï§ 92 Ported v6 ï§ 93 France ï§ 95 Benchmarking ï§ 98 ST Real World Performance ï§ 2000 Dot.Com ï§ 2001 Quest ï§ 2002 Oracle OEM 10g ï§ 2005 Embarcadero ï§ DB Optimizer ï§ Delphix When not being a Geek - Have a little 4 year old boy who takes up all my time
- 5. Typical Architecture DatabaseDatabase File systemFile system ProductionProduction InstanceInstance DatabaseDatabase File systemFile system DevelopmentDevelopment InstanceInstance DatabaseDatabase File systemFile system QAQA InstanceInstance DatabaseDatabase UATUAT InstanceInstance File systemFile system
- 6. Database Virtualization DevelopmentDevelopment InstanceInstance DatabaseDatabase ProductionProduction InstanceInstance File systemFile system vDatabasevDatabase QAQA InstanceInstance UATUAT InstanceInstance vDatabasevDatabase vDatabasevDatabase NFSNFS SourceSource ClonesClones FiberFiber ChannelChannel
- 7. My Goal Simplify the information and empower the DBA
- 8. How do you tune a Database? âDatabase is running slow!â âąWhat : âą first step? âą questions do you ask? âą tools? Do you have a repeatable method?
- 9. What statistics do you look at?
- 10. Launch: Pressure Midnight January 28, 1986 Lives are on the line Thanks to Edward Tufte
- 11. 13 Pages Faxed
- 12. Original Engineering data only showed damage ââdamages at the hottestdamages at the hottest and coldest temperatureâand coldest temperatureâ -- managementmanagement
- 14. Clearer 1. Include successes 2. Mark Differences 3. Normalize same temp 4. Scale known vs unknown 5555 6565 75756060 7070 8080 44 88 1212 44 88 1212 3030 4040 50503535 4545 XX
- 15. Difficult ï§ NASA Engineers Fail ï§ Congressional Investigators Fail ï§ Data Visualization is Difficult But ⊠Lack of Clarity can be devastating
- 16. What statistics do you look at? AASAAS
- 17. Solutions âą Clear Identification âą Know how to identify problems and issues âą Access to details âą Provide solutions and/or information to address the issues âą Graphics âą Easy understanding, effective communication and discussion
- 18. First Step: Graphics âThe humans ⊠are exceptionally good at parsing visual information, especially when that information is coded by color and/or .â Knowledge representation in cognitive science. Westbury, C. & Wilensky, U. (1998) motionmotion
- 19. Why Use Graphics    You can't imagine how many times I was told that nobody wanted or would use graphics ⊠-- Jef Raskin, the creator of the Macintosh Infocus â (overhead projectors) sited a study that humans can parse graphical information 400,000 times faster than textual data
- 20. Counties in US ï§ 3101 Counties ï§ 50 pages
- 21. âIf I can't picture it, I can't understand itâ Anscombe's Quartet I II III IV x y x y x y x y 10 8.04 10 9.14 10 7.46 8 6.58 8 6.95 8 8.14 8 6.77 8 5.76 13 7.58 13 8.74 13 12.74 8 7.71 9 8.81 9 8.77 9 7.11 8 8.84 11 8.33 11 9.26 11 7.81 8 8.47 14 9.96 14 8.1 14 8.84 8 7.04 6 7.24 6 6.13 6 6.08 8 5.25 4 4.26 4 3.1 4 5.39 19 12.5 12 10.84 12 9.13 12 8.15 8 5.56 7 4.82 7 7.26 7 6.42 8 7.91 5 5.68 5 4.74 5 5.73 8 6.89 Average 9 7.5 9 7.5 9 7.5 9 7.5 Standard Deviation 3.31 2.03 3.31 2.03 3.31 2.03 3.31 2.03 Linear Regression 1.33 1.33 1.33 1.33 - Albert Einstein- Albert Einstein
- 22. Graphics for Anscombeâs Quartet
- 23. What is a day in the life look likeWhat is a day in the life look like for a DBA who has performancefor a DBA who has performance issues?issues? Tuning the Database Anscombe's Quartet I II III IV x y x y x y x y Average 9 7.5 9 7.5 9 7.5 9 7.5 Standard Deviation 3.31 2.03 3.31 2.03 3.31 2.03 3.31 2.03 Linear Regression 1.33 1.33 1.33 1.33 ComplexComplex AveragesAverages
- 24. LOADLOAD TopTop ActivityActivity SQLSQL EventsEvents SessionsSessions Max CPUMax CPU (yard stick)(yard stick) How Can We Open the Black Box?
- 25. LOADLOAD TopTop ActivityActivity SQLSQL EventsEvents SessionsSessions Get DetailsGet Details Click hereClick here Max CPUMax CPU (yard stick)(yard stick) How Can We Open the Black Box?
- 26. How Can We Open the Black Box? OEMOEM ASHMON/SASHASHMON/SASH DB OptimizerDB Optimizer âąPowerful - Identifies issues quickly and powerfully âąInteractive - Allows exploring the data âąEasy - Understandable by everyone, DBA, Dev and Managers !
- 28. Before Tuning Oracle, Tune the Machine Make sure the machine is healthy before tuning Oracle ï§ CPU => use run queue, < 2 * #CPU ï§ Memory => page out VMSTAT
- 29. Sections ï§ Statspack ï§ ASH ï§ AAS ï§ OEM 10g ï§ Buffer Cache ï§ IO ï§ Redo ï§ Enqueues ï§ Shared Pool ï§ SQL*Net ï§ SQL Tuning
- 30. Do You Want? Engineering Data?Engineering Data?
- 31. Do You Want? Pretty PicturesPretty Pictures
- 32. Do You Want? Clean and ClearClean and Clear ? ? ? ?? ? ? ? ? ?? ?
- 33. Imagine Trying to Drive your Car And is updated once and hourAnd is updated once and hour Or would you like it toOr would you like it to look âŠlook ⊠Would you want your dashboard to look like :Would you want your dashboard to look like :
- 34. Or This
- 35. Embarcadero 35
- 36. Summary 1.Machine - vmstat ï§ Memory, CPU (we can see IO response in Oracle) 1.Database - AAS ï§ Use wait interface and graphics ï§ Identify machine, application, database or SQL 1.SQL - VST ï§ Indexes, stats, execution path ï§ Visual SQL Tuning
- 37. Bibliography www.simple-talk.com/sql/performance/designing-efficient-sql-a-visual-approach/www.simple-talk.com/sql/performance/designing-efficient-sql-a-visual-approach/ Refactoring SQL Applications â Stephane Faroult Troubleshooting Oracle Performance â Christian Antognini SQL Tuning â Dan Tow Cost-Based Oracle Fundamentals â Jonathan Lewis
- 38. Books ï§ The Visual Display of Quantitative Information ï§ Eduard Tufte ï§ Oracle Wait Interface ï§ Kirtikumar Deshpande, K. Gopalakrishnan ï§ SQL Tuning ï§ Dan Tow DesignDesign WaitsWaits SQLSQL
- 39. Books ï§ Jonathan Lewis ï§ Cost-Based Oracle (Tough Read) ï§ Practical Oracle 8i (easy read) ï§ Oracle Insights ï§ Kyle Hailey & Oaktable Members DirectDirect MemoryMemory AttachAttach OracleOracle OptimizerOptimizer
- 41. When to Tune 1. Machine a) CPU ï§ Response times skewed ï§ 100% CPU might be fine ï§ Users wait in queue (run queue) => machine underpowered a) Memory ï§ Paging ï§ Wait times skewed (ex : latch free) ï§ Erratic response times ( ex : ls ) 1. Oracle 1) Waits > CPU ? ï§ tune waits 1) CPU > 100% ? ï§ tune top CPU SQL 1) Else ï§ Itâs the application Oracle LoadOracle Load (AAS)(AAS) Top SessionTop Session Top WaitTop Wait Top SQLTop SQL SQL DetailSQL Detail Session DetailSession Detail File DetailFile DetailObject DetailObject Detail Wait DetailWait Detail HostHost AAS >AAS > #CPU#CPU AAS > 1AAS > 1 Waits >Waits > CPUCPU CPU >CPU > WaitsWaits CPUCPU MemoryMemory
- 42. Summary 1.Database - AAS ï§ Profile database ï§ Use wait interface and graphics ï§ Identify machine, application, database or SQL 1.SQL - VST ï§ Indexes, stats, execution path ï§ Visual SQL Tuning
Editor's Notes
- #3: In Oracle Support I learned more faster than I think I could have anywhere. Porting gave me my first appreciation for the shareable nature of Oracle code and also a bit of disbelief that it worked as well as it did. Oracle France gave me an opportunity to concentrate on the Oracle kernel. At Oracle France I had 3 amazing experiences. First was being sent to the Europecar site where I first met a couple of the people who would later become the founding members of the Oaktable, James Morle and Anjo Kolk. The Europecar site introduced me to a fellow name Roger Sanders who first showed me the wait interface before anyone knew what it was. Roger not only used it but read it directly from shared memory without using SQL. Soon after Europecar I began to be sent often to benchmarks at Digital Europe. These benchmarks were some of my favorite work at Oracle. The benchmarks usually consisted of installing some unknown Oracle customer application and then having a few days to make it run as fast as possible. I first started using TCL/TK and direct shared memory access (DMA) at Digital Europe and got solid hands on tuning experience testing things like striping redo and proving it was faster long before people gave up arguing that this was bad from a theoretical point of view. Finally in France, my boss, Jean Yves Caleca was by far the best boss I ever had, but on top of that he was wonderful at exploring the depths of Oracle and explaining it to others, teaching me much about the internals of block structure, UNDO, REDO and Freelsits. I came back from France wanting to do performance work and especially graphical monitoring. The kernel performance group had limited scope in that domain, so I left for a dot com where I had my first run as the sole DBA for everything, backup, recovery, performance, installation and administration. I was called away by Quest who had my favorite performance tool Spotlight. It turns out thought that scope for expanding Spotlight was limited so I jumped at the chance in 2002 to restructure Oracle OEM. The work at OEM Iâm proud of but still want to do much more to make performance tuning faster, easier and more graphical.
- #4: In Oracle Support I learned more faster than I think I could have anywhere. Porting gave me my first appreciation for the shareable nature of Oracle code and also a bit of disbelief that it worked as well as it did. Oracle France gave me an opportunity to concentrate on the Oracle kernel. At Oracle France I had 3 amazing experiences. First was being sent to the Europecar site where I first met a couple of the people who would later become the founding members of the Oaktable, James Morle and Anjo Kolk. The Europecar site introduced me to a fellow name Roger Sanders who first showed me the wait interface before anyone knew what it was. Roger not only used it but read it directly from shared memory without using SQL. Soon after Europecar I began to be sent often to benchmarks at Digital Europe. These benchmarks were some of my favorite work at Oracle. The benchmarks usually consisted of installing some unknown Oracle customer application and then having a few days to make it run as fast as possible. I first started using TCL/TK and direct shared memory access (DMA) at Digital Europe and got solid hands on tuning experience testing things like striping redo and proving it was faster long before people gave up arguing that this was bad from a theoretical point of view. Finally in France, my boss, Jean Yves Caleca was by far the best boss I ever had, but on top of that he was wonderful at exploring the depths of Oracle and explaining it to others, teaching me much about the internals of block structure, UNDO, REDO and Freelsits. I came back from France wanting to do performance work and especially graphical monitoring. The kernel performance group had limited scope in that domain, so I left for a dot com where I had my first run as the sole DBA for everything, backup, recovery, performance, installation and administration. I was called away by Quest who had my favorite performance tool Spotlight. It turns out thought that scope for expanding Spotlight was limited so I jumped at the chance in 2002 to restructure Oracle OEM. The work at OEM Iâm proud of but still want to do much more to make performance tuning faster, easier and more graphical.
- #5: In Oracle Support I learned more faster than I think I could have anywhere. Porting gave me my first appreciation for the shareable nature of Oracle code and also a bit of disbelief that it worked as well as it did. Oracle France gave me an opportunity to concentrate on the Oracle kernel. At Oracle France I had 3 amazing experiences. First was being sent to the Europecar site where I first met a couple of the people who would later become the founding members of the Oaktable, James Morle and Anjo Kolk. The Europecar site introduced me to a fellow name Roger Sanders who first showed me the wait interface before anyone knew what it was. Roger not only used it but read it directly from shared memory without using SQL. Soon after Europecar I began to be sent often to benchmarks at Digital Europe. These benchmarks were some of my favorite work at Oracle. The benchmarks usually consisted of installing some unknown Oracle customer application and then having a few days to make it run as fast as possible. I first started using TCL/TK and direct shared memory access (DMA) at Digital Europe and got solid hands on tuning experience testing things like striping redo and proving it was faster long before people gave up arguing that this was bad from a theoretical point of view. Finally in France, my boss, Jean Yves Caleca was by far the best boss I ever had, but on top of that he was wonderful at exploring the depths of Oracle and explaining it to others, teaching me much about the internals of block structure, UNDO, REDO and Freelsits. I came back from France wanting to do performance work and especially graphical monitoring. The kernel performance group had limited scope in that domain, so I left for a dot com where I had my first run as the sole DBA for everything, backup, recovery, performance, installation and administration. I was called away by Quest who had my favorite performance tool Spotlight. It turns out thought that scope for expanding Spotlight was limited so I jumped at the chance in 2002 to restructure Oracle OEM. The work at OEM Iâm proud of but still want to do much more to make performance tuning faster, easier and more graphical.
- #20: What allows Oracle, all the dials and knobs, to be the fastest, most robust database on the market also make it one of the most complicated on the market. For those few users that know and love the 1000s of performance options in Oracle, access to those performance options through sql and C code is the defacto standard. For seasoned users it is often difficult to understand why anyone would want to be limited by a GUI which can often be slower, and almost always lacking the latest commands allowed through interfaces such as SQL and C. On the OEM side, when a new tuning feature in the kernel is externalized in OEM (Oracle Enterprise Manager) it is often difficult to see the forest for the tree, or where and how that new feature fits into the grand scheme of things.
- #28: This presentation presented a challenge because many of the concepts were like the chicken and the egg. In order to explain one I needed the other. I âve tried to keep the subjects as linear as possible but sometimes I interweave from one to another.
- #42: In order to tune an Oracle database the first step in a complete analysis is to verify the machine because there are a couple of factors that can only be clearly determined by looking at machine statistics. Those two factors are Memory Usage CPU Usage Memory and CPU problems will have tell tale repercussions on Oracle performance statistics and thus can be deduced from just looking at the Oracle statistics, but it is clear just to start with the machine statistics. CPU For CPU, we check the ârun queueâ which is the number of processes that are ready to run but have to wait for the CPU. A machine free of CPU contention would have a run queue of 0 and could have CPU usage near 100% at the same time. A high CPU usage can be a good sign that the system is being utilized fully. On the other hand a high run queue will indicated that there is more demand for CPU than CPU power available. High run queue can be determined via Oracle statistics by looking at ASH data and seeing if more sessions are marked as being on the CPU than the number of CPUs available. For example if there are 4 sessions average active on CPU in the ASH data and only 2 CPUs then the machine is CPU bound. Solutions for high run queue are either to add more processors or reduce the load on the CPU. If the CPU is mainly being used by Oracle, then that is going to mean tuning the application and ther SQL queries. Memory If the machine is paging out to disk it means there is a memory crunch and can dramatically slow down Oracle. Oracle will sometimes indicate a paging problem through a spike in âlatch freeâ waits but the only guarenteed method of diagnosing this problem is looking at the machine statistics. Machines have statistics for paging and free memory. Often there can be some free memory even when there is paging out because machines start paging out before memory is completely filled. Solutions if the machine is paging out are either to add more memory or to reduce memory usage. Memory usage can be reduced by reducing Oracle cache sizes or reducing Oracle session memory usage.