Troubleshooting Dennis Shasha and Philippe Bonnet, 2013.

Slides:



Advertisements
Similar presentations
1 CS 5226: Database Administration and Performance Tuning.
Advertisements

Database Tuning Principles, Experiments and Troubleshooting Techniques Baseado nos slides do tutorial com o mesmo nome da autoria de: Dennis Shasha
Performance Tuning Compiled from: Oracle Database Administration, Session 13, Performance, Harvard U Oracle Server Tuning Accelerator, David Scott, Intec.
Chapter 9. Performance Management Enterprise wide endeavor Research and ascertain all performance problems – not just DBMS Five factors influence DB performance.
Module 13: Performance Tuning. Overview Performance tuning methodologies Instance level Database level Application level Overview of tools and techniques.
Overview of performance tuning strategies Oracle Performance Tuning Allan Young June 2008.
Adam Jorgensen Pragmatic Works Performance Optimization in SQL Server Analysis Services 2008.
Database System Concepts and Architecture
Module 17 Tracing Access to SQL Server 2008 R2. Module Overview Capturing Activity using SQL Server Profiler Improving Performance with the Database Engine.
Performance and Scalability. Optimizing PerformanceScaling UpScaling Out.
Keeping our websites running - troubleshooting with Appdynamics Benoit Villaumie Lead Architect Guillaume Postaire Infrastructure Manager.
Troubleshooting Dennis Shasha and Philippe Bonnet, 2013.
AOBD 07/08H. Galhardas DBMS Performance Monitoring.
Chapter Physical Database Design Methodology Software & Hardware Mapping Logical Design to DBMS Physical Implementation Security Implementation Monitoring.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 11 Database Performance Tuning and Query Optimization.
Measuring Performance Chapter 12 CSE807. Performance Measurement To assist in guaranteeing Service Level Agreements For capacity planning For troubleshooting.
1 External Sorting for Query Processing Yanlei Diao UMass Amherst Feb 27, 2007 Slides Courtesy of R. Ramakrishnan and J. Gehrke.
Chapter 9 Overview  Reasons to monitor SQL Server  Performance Monitoring and Tuning  Tools for Monitoring SQL Server  Common Monitoring and Tuning.
Module 8: Monitoring SQL Server for Performance. Overview Why to Monitor SQL Server Performance Monitoring and Tuning Tools for Monitoring SQL Server.
Connect with life Praveen Srvatsa Director | AsthraSoft Consulting Microsoft Regional Director, Bangalore Microsoft MVP, ASP.NET.
Copyright © 2007 Quest Software The Changing Role of SQL Server DBA’s Bryan Oliver SQL Server Domain Expert Quest Software.
Chapter 1 Overview of Databases and Transaction Processing.
Module 15: Monitoring. Overview Formulate requirements and identify resources to monitor in a database environment Types of monitoring that can be carried.
1 CSE544 Database Architecture Tuesday, February 1 st, 2011 Slides courtesy of Magda Balazinska.
Module 8: Server Management. Overview Server-level and instance-level resources such as memory and processes Database-level resources such as logical.
Performance and Scalability. Performance and Scalability Challenges Optimizing PerformanceScaling UpScaling Out.
Continuous resource monitoring for self-predicting DBMS Dushyanth Narayanan 1 Eno Thereska 2 Anastassia Ailamaki 2 1 Microsoft Research-Cambridge, 2 Carnegie.
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 11 Database Performance Tuning and Query Optimization.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 10 Database Performance Tuning and Query Optimization.
2 Copyright © 2006, Oracle. All rights reserved. Performance Tuning: Overview.
CSC271 Database Systems Lecture # 30.
Introduction. Outline What is database tuning What is changing The trends that impact database systems and their applications What is NOT changing The.
Profiling Grid Data Transfer Protocols and Servers George Kola, Tevfik Kosar and Miron Livny University of Wisconsin-Madison USA.
March 19981© Dennis Adams Associates Tuning Oracle: Key Considerations Dennis Adams 25 March 1998.
Physical Database Design Chapter 6. Physical Design and implementation 1.Translate global logical data model for target DBMS  1.1Design base relations.
© Dennis Shasha, Philippe Bonnet – 2013 Communicating with the Outside.
Oracle Tuning Considerations. Agenda Why Tune ? Why Tune ? Ways to Improve Performance Ways to Improve Performance Hardware Hardware Software Software.
Oracle Tuning Ashok Kapur Hawkeye Technology, Inc.
© Dennis Shasha, Alberto Lerner, Philippe Bonnet 2004 DBMS Performance Monitoring.
1 Wenguang WangRichard B. Bunt Department of Computer Science University of Saskatchewan November 14, 2000 Simulating DB2 Buffer Pool Management.
BW Know-How Call : Performance Tuning dial-in phone numbers! U.S. Toll-free: (877) International: (612) Passcode: “BW”
DBI313. MetricOLTPDWLog Read/Write mixMostly reads, smaller # of rows at a time Scan intensive, large portions of data at a time, bulk loading Mostly.
Oracle9i Performance Tuning Chapter 12 Tuning Tools.
© Dennis Shasha, Philippe Bonnet 2001 Log Tuning.
SQLRX – SQL Server Administration – Tips From the Trenches SQL Server Administration – Tips From the Trenches Troubleshooting Reports of Sudden Slowdowns.
By Shanna Epstein IS 257 September 16, Cnet.com Provides information, tools, and advice to help customers decide what to buy and how to get the.
© Dennis Shasha, Alberto Lerner, Philippe Bonnet 2004 DBMS Performance Monitoring.
CS338Parallel and Distributed Databases11-1 Parallel and Distributed Databases Lecture Topics Multi-CPU and distributed systems Monolithic system Client–server.
Communicating with the Outside. Hardware [Processor(s), Disk(s), Memory] Operating System Concurrency ControlRecovery Storage Subsystem Indexes Query.
CERN IT Department CH-1211 Geneva 23 Switzerland t Oracle Tutorials CERN June 8 th, 2012 Performance Tuning.
Troubleshooting SQL Server Performance: Tips &Tools Amit Khandelwal.
Physical Database Design Purpose- translate the logical description of data into the technical specifications for storing and retrieving data Goal - create.
MISSION CRITICAL COMPUTING Siebel Database Considerations.
Query Optimization CMPE 226 Database Systems By, Arjun Gangisetty
Your Data Any Place, Any Time Performance and Scalability.
1 Copyright © 2005, Oracle. All rights reserved. Following a Tuning Methodology.
Lock Tuning. Overview Data definition language (DDL) statements are considered harmful DDL is the language used to access and manipulate catalog or metadata.
Database Systems, 8 th Edition SQL Performance Tuning Evaluated from client perspective –Most current relational DBMSs perform automatic query optimization.
Copyright Sammamish Software Services All rights reserved. 1 Prog 140  SQL Server Performance Monitoring and Tuning.
SQL Advanced Monitoring Using DMV, Extended Events and Service Broker Javier Villegas – DBA | MCP | MCTS.
3 Copyright © 2006, Oracle. All rights reserved. Designing and Developing for Performance.
CERN IT Department CH-1211 Genève 23 Switzerland t Load testing & benchmarks on Oracle RAC Romain Basset – IT PSS DP.
Oracle Database Architectural Components
Session Name Pelin ATICI SQL Premier Field Engineer.
© Dennis Shasha, Alberto Lerner, Philippe Bonnet 2004 DBMS Performance Monitoring.
SQL Database Management
SQL Server Monitoring Overview
Predictive Performance
Troubleshooting Techniques(*)
Performance And Scalability In Oracle9i And SQL Server 2000
Presentation transcript:

Troubleshooting Dennis Shasha and Philippe Bonnet, 2013

Outline DBMS architecture overview – Overview for now – More details as we progress through lectures Troubleshooting and experimentation Troubleshooting methodologies – Resource consumption model – Time-spent Dennis Shasha and Philippe Bonnet, 2013

Traditional Architecture DBMS Application OS HW Q DATA Result Set DBMS Client Dennis Shasha and Philippe Bonnet, 2013

DBMS Components Query Processor Concurrency ControlRecovery Storage Subsystem Indexes Compiler Parser Execution Engine Buffer Dennis Shasha and Philippe Bonnet, 2013

DB2 9.7 Process Dennis Shasha and Philippe Bonnet, 2013 Source: Exercise 1: Is intra-query parallelism possible with this process model? In other words, can a query be executed in parallel within a same instance (or partition)? Exercise 1: Is intra-query parallelism possible with this process model? In other words, can a query be executed in parallel within a same instance (or partition)?

DB Process Architecture Source: Dennis Shasha and Philippe Bonnet, 2013 No need to know much more about the process abstractions. We will cover much more on the memory abstractions (log tuning), and on the communication abstractions (tuning the application interface, tuning across instances).

MySQL Dennis Shasha and Philippe Bonnet, 2013 Source:

Troubleshooting: Why Production – Users/manager complaints. – Needs monitoring. What is going on NOW? – Once identified, a problem should be represented in a synthetic form (so that others can avoid the problem, or as a request for new features from DBMS/OS) Test – New application / New system / New functionalities / New scale – Can system keep performance up in new settings? – Needs Dennis Shasha and Philippe Bonnet, 2013

Troubleshooting: How You MUST measure system performance (black box) – Profiling tools You MUST instrument your system to get some insight about the internal processes (white box) – System instrumentation You MUST follow a systematic approach for troubleshooting / experimentation – Scientific Method – Troubleshooting Dennis Shasha and Philippe Bonnet, 2013

Experimental Framework 1.System – Application + DBMS + OS + HW – Parameters (fixed/factors) 2.Metrics – Throughput / Response Time – DBMS performance indicators – OS performance indicators 3.Workload – Actual users (production), replay trace or synthetic workload (e.g., TPC benchmark) 4.Experiments – What factor to Dennis Shasha and Philippe Bonnet, 2013 Exercise 2: Is throughput always the inverse of response time? Exercise 2: Is throughput always the inverse of response time? Exercise 3: Define an experiment to measure the write throughput of the file system on your laptop Exercise 3: Define an experiment to measure the write throughput of the file system on your laptop

Performance Indicators Type – Counter – Watermark – Gauge – Timestamp Scope – System-wide (snapshot) vs. workload-specific (activity detail) Collection – switched on/off vs. triggered by a specific event – File dump vs. materialized view Frequency of update of the materialized view Access – Table functions, views, XML files – Alert triggered by a specific Dennis Shasha and Philippe Bonnet, 2013 LOOKUP: DB2 monitor elements and interfaces for monitoring, Oracle dynamic performance viewsDB2 monitor elementsnterfaces for monitoringOracle dynamic performance views Exercise 4: What are system-wide indicators good for? Exercise 4: What are system-wide indicators good for?

Example Statement number: 1 select C_NAME, N_NAME from DBA.CUSTOMER join DBA.NATION on C_NATIONKEY = N_NATIONKEY where C_ACCTBAL > 0 Number of rows retrieved is: Number of rows sent to output is: 0 Elapsed Time is: seconds … Buffer pool data logical reads = Buffer pool data physical reads = Buffer pool data writes = 0 Buffer pool index logical reads = Buffer pool index physical reads = 552 Buffer pool index writes = 0 Total buffer pool read time (ms) = Total buffer pool write time (ms) = 0 … Summary of Results ================== Elapsed Agent CPU Rows Rows Statement # Time (s) Time (s) Fetched Printed DBMS OS Exercise 6: Which are the profiling tools on Azure? Exercise 6: Which are the profiling tools on Azure? Exercise 5: What are the 11 system wide indicators recommended for DB2 10.1?11 system wide indicators Exercise 5: What are the 11 system wide indicators recommended for DB2 10.1?11 system wide indicators Windows: Performance monitor Linux: iostat, vmstat More on this in tuning the guts.

Troubleshooting Methodologies Resource Consumption Model (Chapter 7) Primary, DBMS system resources Applications as consumers Instrumentation through counters/watermarks/gauge Time Spent Model response time = execution time + wait time Instrumentation through Dennis Shasha and Philippe Bonnet, 2013 Exercise 7: Do Extended events follow the resource consumption or time spent model?Extended events Exercise 7: Do Extended events follow the resource consumption or time spent model?Extended events

Resource Consumption Dennis Shasha and Philippe Bonnet, 2013 An overloading high-level consumer A poorly parameterized subsystem An overloaded primary resource Effects are not always felt first where the cause is!

Resource Consumption Dennis Shasha and Philippe Bonnet, 2013 Question 1: Are critical queries being served in the most efficient manner? Question 2: Are subsystems making optimal use of resources? Question 3: Are there enough primary resources available? Extract indicators to answer the following questions

Dennis Shasha and Philippe Bonnet, 2013 Which are the critical queries? Ask users. Use query log to find queries that take longest. Resource Usage Check out system-wide performance indicators. Use rules of thumbs to check whether they are ok.

Time Spent Model Given a critical query / session Where does the time go? – Throughout DBMS/OS/HW components – Waiting / Executing – Find out which components cause a session to be Dennis Shasha and Philippe Bonnet, 2013 LOOK UP: Cary Millsap’s book: Oracle Operational Timing Presentation Issues: How to instrument ONLY a given critical query/sesssion What timestamps indicators are available? Issues: How to instrument ONLY a given critical query/sesssion What timestamps indicators are available?

@ Dennis Shasha and Philippe Bonnet, 2013 Exercise 8: Assume your DBMS is SQL Server How can you answer the following questions: How many IOs are performed when executing a given query? How many pages are actually read? How much space is used in the buffer pool? How much time is spent performing those IOs? What percentage of the total execution time does it take to perform those IOs? What portion of those IOs are sequential? How much overhead is there in obtaining the answer to those questions? Exercise 8: Assume your DBMS is SQL Server How can you answer the following questions: How many IOs are performed when executing a given query? How many pages are actually read? How much space is used in the buffer pool? How much time is spent performing those IOs? What percentage of the total execution time does it take to perform those IOs? What portion of those IOs are sequential? How much overhead is there in obtaining the answer to those questions?