Analyzing the Energy Efficiency of a Database Server Hanskamal Patel SE 521.

Slides:



Advertisements
Similar presentations
Network II.5 simulator ..
Advertisements

Module 13: Performance Tuning. Overview Performance tuning methodologies Instance level Database level Application level Overview of tools and techniques.
CA 714CA Midterm Review. C5 Cache Optimization Reduce miss penalty –Hardware and software Reduce miss rate –Hardware and software Reduce hit time –Hardware.
Daniel Schall, Volker Höfner, Prof. Dr. Theo Härder TU Kaiserslautern.
Storing Data: Disks and Files: Chapter 9
Query Processing and Optimizing on SSDs Flash Group Qingling Cao
Building a Distributed Full-Text Index for the Web S. Melnik, S. Raghavan, B.Yang, H. Garcia-Molina.
High Performance Analytical Appliance MPP Database Server Platform for high performance Prebuilt appliance with HW & SW included and optimally configured.
Chapter 5 Computing Components. The (META) BIG IDEA Cool, idea but maybe too big DATA – Must be stored somewhere in a storage device PROCESSING – Data.
1 HYRISE – A Main Memory Hybrid Storage Engine By: Martin Grund, Jens Krüger, Hasso Plattner, Alexander Zeier, Philippe Cudre-Mauroux, Samuel Madden, VLDB.
Thin Servers with Smart Pipes: Designing SoC Accelerators for Memcached Bohua Kou Jing gao.
Towards Energy Efficient Hadoop Wednesday, June 10, 2009 Santa Clara Marriott Yanpei Chen, Laura Keys, Randy Katz RAD Lab, UC Berkeley.
Shimin Chen Big Data Reading Group Presented and modified by Randall Parabicoli.
Shimin Chen Big Data Reading Group.  Energy efficiency of: ◦ Single-machine instance of DBMS ◦ Standard server-grade hardware components ◦ A wide spectrum.
Energy-efficient Cluster Computing with FAWN: Workloads and Implications Vijay Vasudevan, David Andersen, Michael Kaminsky*, Lawrence Tan, Jason Franklin,
Presented by Marie-Gisele Assigue Hon Shea Thursday, March 31 st 2011.
Towards Energy Efficient MapReduce Yanpei Chen, Laura Keys, Randy H. Katz University of California, Berkeley LoCal Retreat June 2009.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 11 Database Performance Tuning and Query Optimization.
Chapter 8 Physical Database Design. McGraw-Hill/Irwin © 2004 The McGraw-Hill Companies, Inc. All rights reserved. Outline Overview of Physical Database.
Introduction to Database Systems 1 The Storage Hierarchy and Magnetic Disks Storage Technology: Topic 1.
H-1 Network Management Network management is the process of controlling a complex data network to maximize its efficiency and productivity The overall.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1 Preview of Oracle Database 12 c In-Memory Option Thomas Kyte
Towards Eco-friendly Database Management Systems W. Lang, J. M. Patel (U Wisconsin), CIDR 2009 Shimin Chen Big Data Reading Group.
Lecture 11: DMBS Internals
C-Store: Column Stores over Solid State Drives Jianlin Feng School of Software SUN YAT-SEN UNIVERSITY Jun 19, 2009.
Flash research report Da Zhou Outline Query Processing Techniques for Solid St ate Drives (Research Paper) Join Processing for Flash SSDs: Rememb.
Database Systems Design, Implementation, and Management Coronel | Morris 11e ©2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 10 Database Performance Tuning and Query Optimization.
© Stavros Harizopoulos 2006 Performance Tradeoffs in Read-Optimized Databases Stavros Harizopoulos MIT CSAIL joint work with: Velen Liang, Daniel Abadi,
Parallel Programming Models Jihad El-Sana These slides are based on the book: Introduction to Parallel Computing, Blaise Barney, Lawrence Livermore National.
Introduction to Hadoop and HDFS
Data Warehousing 1 Lecture-24 Need for Speed: Parallelism Virtual University of Pakistan Ahsan Abdullah Assoc. Prof. & Head Center for Agro-Informatics.
MonetDB/X100 hyper-pipelining query execution Peter Boncz, Marcin Zukowski, Niels Nes.
Performance Tradeoffs in Read-Optimized Databases Stavros Harizopoulos * MIT CSAIL joint work with: Velen Liang, Daniel Abadi, and Sam Madden massachusetts.
© Stavros Harizopoulos 2006 Performance Tradeoffs in Read- Optimized Databases: from a Data Layout Perspective Stavros Harizopoulos MIT CSAIL Modified.
DONE-08 Sizing and Performance Tuning N-Tier Applications Mike Furgal Performance Manager Progress Software
Towards Dynamic Green-Sizing for Database Servers Mustafa Korkmaz, Alexey Karyakin, Martin Karsten, Kenneth Salem University of Waterloo.
VGreen: A System for Energy Efficient Manager in Virtualized Environments G. Dhiman, G Marchetti, T Rosing ISLPED 2009.
DMBS Internals I. What Should a DBMS Do? Store large amounts of data Process queries efficiently Allow multiple users to access the database concurrently.
Virtualization and Databases Ashraf Aboulnaga University of Waterloo.
1 MSRBot Web Crawler Dennis Fetterly Microsoft Research Silicon Valley Lab © Microsoft Corporation.
Copyright 2007, Information Builders. Slide 1 Machine Sizing and Scalability Mark Nesson, Vashti Ragoonath June 2008.
Chapter 8 Physical Database Design. Outline Overview of Physical Database Design Inputs of Physical Database Design File Structures Query Optimization.
Infrastructure for Data Warehouses. Basics Of Data Access Data Store Machine Memory Buffer Memory Cache Data Store Buffer Bus Structure.
Mapping the Data Warehouse to a Multiprocessor Architecture
The Sort Benchmark AlgorithmsSolid State Disks External Memory Multiway Mergesort  Phase 1: Run Formation  Phase 2: Merge Runs  Careful parameter selection.
An Integrated GPU Power and Performance Model (ISCA’10, June 19–23, 2010, Saint-Malo, France. International Symposium on Computer Architecture)
1 Chapter 9 Tuning Table Access. 2 Overview Improve performance of access to single table Explain access methods – Full Table Scan – Index – Partition-level.
Unit - 4 Introduction to the Other Databases.  Introduction :-  Today single CPU based architecture is not capable enough for the modern database.
DMBS Internals I February 24 th, What Should a DBMS Do? Store large amounts of data Process queries efficiently Allow multiple users to access the.
DMBS Internals I. What Should a DBMS Do? Store large amounts of data Process queries efficiently Allow multiple users to access the database concurrently.
Database Management Systems, R. Ramakrishnan and J. Gehrke1 External Sorting Chapter 11.
What Should a DBMS Do? Store large amounts of data Process queries efficiently Allow multiple users to access the database concurrently and safely. Provide.
Introduction to Performance Tuning Chia-heng Tu PAS Lab Summer Workshop 2009 June 30,
The Sort Benchmark AlgorithmsSolid State Disks External Memory Multiway Mergesort  Phase 1: Run Formation  Phase 2: Merge Runs  Careful parameter selection.
Hardware vs. Software Question 1 What is hardware?
Running virtualized Hadoop, does it make sense?
Selective Code Compression Scheme for Embedded System
Hadoop Clusters Tess Fulkerson.
Software Architecture in Practice
Database Performance Tuning and Query Optimization
Lecture 11: DMBS Internals
Overview Introduction VPS Understanding VPS Architecture
Mapping the Data Warehouse to a Multiprocessor Architecture
Akshay Tomar Prateek Singh Lohchubh
KISS-Tree: Smart Latch-Free In-Memory Indexing on Modern Architectures
Cloud computing mechanisms
Chapter 11 Database Performance Tuning and Query Optimization
Database System Architectures
The Gamma Database Machine Project
Presentation transcript:

Analyzing the Energy Efficiency of a Database Server Hanskamal Patel SE 521

Article Analyzing the Energy Efficiency of a Database Server – Dimitris Tsirogiannis – University of Toronto – Stavros Harizopoulos – HP Labs – Mehul A. Shah – HP Labs

Introduction Evaluating database system in terms of performance is measured in task per second or queries per second. Similarly, energy-efficiency is determined by the measure of completed task per energy/Queries per Joule. Improving performance is hardware/platform oriented or workload-management oriented. Exploring ways to improve energy efficiency of a single- machine database server.

Test Machine Configuration

Power Breakdown About half of the peak power is idle system – Two CPU’s – Fixed RAM Power – Board components – SDD and HDD Minimal Power Left side of the chart is active power consumption – CPU is dominant component – SSD and HDD draw similar power

CPU Usage vs. Power

What affects energy efficiency? EE = Work/Energy = Performance/Power Several options affect power-use and potentially affect energy efficiency – CPU cycles to fetch data from disk – Scans, record access, compressions, sorting, and joining Energy efficiency can be improved but it may sacrifice performance

Energy efficiency vs. Performance Experimented with five different overhead kernels – Parallel performing, cache-conscious hash join, sorting, alphasort and parallel merging High performance storage engine that supports column and row oriented database scans. PostgreSQL and System-X DBMS

Performance vs. Energy

Assembling data-management architectures Scale-up – Shared memory and shared disk – Choosing the balance of components and power down unneeded resources Scale-out – Share nothing – Single node configurations connected by scaled network – Choose energy efficient components for one node and performance optimized for another

Power Profiles of Hardware Components RAM – RAM is responsible for 20% of the power consumption and stays the same throughout – Only way to vary power usage by memory is to physically remove the modules from the board

Power Profiles of Hardware Components Disks – Both HDD and SSD in the configuration – Supports active and idle stages, consuming different amount of power – 15% in the active stage Test Configuration – Raid-0 configuration for both HDD and HDD – Reading 100GB block size of 128KB

Power Consumption of Disks

Power Profiles of Hardware Components CPU – The two CPU’s are responsible for the 85% of power increase in the system while active – Interested in understanding: How CPU power is affected by database operations and the efficacy of hardware and software power management Developed a set of micro-benchmarks that performs three classes of database operations: hashing, sorting, and scans.

Micro-benchmarks Custom Join Kernel – Hash join algorithm for computing join of two relations in parallel. Sort Kernel – Two in-memory parallel sorting algorithm Scan kernel – Scan uncompressed rows in memory – Scan compressed column on disk

Analyzing Power Consumption

Memory bus utilization

Hashjoin Operator

Sort Operator

Scan Operator

Energy vs. Performance Parameters that have greatest impact on energy – Algorithm/plan selection – Intra-operator parallelism – Inter-query parallelism

Algorithm/Plan selection Access Methods Join Algorithms Complex Queries and Join Ordering

Intra-operator and Inter-query Parallelism Intra-operator parallelism – Parallel hash join – Parallel Sorts Inter-query parallelism – Executing multiple queries at the same time

Implications for Database Computing One size fits all – Collection of nodes, where each node is optimized for specific task – High parallelism, low-frequency, small cache, and simple design CPU – Solid state drives Shared nothing, everything, or in-between – Shared nothing and shared disk Controlling peak power

Conclusion CPU power usage by different operators can vary by up to 60% The best performing system was the most energy efficient Future investigations: – Improving resources across unutilized nodes to save power – Alternative energy efficient hardware for lower fixed-power cost

Questions?