DOCSLIB.ORG

Evaluating Database Self-Tuning Strategies in a Common Extensible Framework

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Evaluating Database Self-Tuning Strategies in a Common Extensible Framework Evaluating Database Self-Tuning Strategies in a Common Extensible Framework Rafael Pereira de Oliveira1, Sergio Lifschitz1, Marcos Kalinowski1, Marx Viana1, Carlos Lucena1, Marcos Antonio Vaz Salles2 1Pontifical Catholic University of Rio de Janeiro (PUC-Rio) 2University of Copenhagen Abstract. Database automatic tuning tools are an essential class of database applications for database administrators (DBAs) and researchers. These self- management systems involve recurring and ubiquitous tasks, such as data ex- traction for workload acquisition and more specific features that depend on the tuning strategy, such as the specification of tuning action types and heuristics. Given the variety of approaches and implementations, it would be desirable to evaluate existing database self-tuning strategies, particularly recent and new heuristics, in a standard testbed. In this paper, we propose a reuse-oriented framework approach towards assessing and comparing automatic relational database tuning strategies. We employ our framework to instantiate three cus- tomized automated database tuning tools extended from our framework kernel, employing strategies using combinations of different tuning actions (indexes, partial indexes, and materialized views) for various RDBMS. Finally, we eval- uate the effectiveness of these tools using a known database benchmark. Our results show that the framework enabled instantiating useful self-tuning tools with a low effort by just extending well-defined framework hot-spots. Hence, sharing it with the database research community may facilitate evolving state of the art on self-tunning strategies by enabling to evaluate different strategies on different RDBMS, serving as a common and extensible testbed. 1. Introduction We may find many different self-tuning systems available to run, externally coupled, or integrated within a DBMS. There is a need for evaluating their effectiveness and efficiency due to the variety of automatic tuning tools, mainly for relational DBMSs. Either we might want to check for existing features that are mandatory for a given application, or we would like to characterize the pros and cons of implemented heuristics when compared with new ones proposed in the literature. These provide the best-expected results for the database system performance. There exist specific tuning tasks that might have automatic support in a given RDBMS, but not others. For example, it is possible to tune database parameters to server hardware with PostgreSQL [PGTune 2019] automatically. Still, it is hard to find tools for automating a variety of physical database design tasks (e.g., creating materialized views or partial indices). It is infeasible for the DBA to, promptly, test and evaluate all possible physical design tuning actions for a given workload, as even index selection is NP-hard [Piatetsky-Shapiro 1983]. Nevertheless, tools to aid in this task exist for other RDBMS [Bruno 2012]. Software reuse is one of the significant goals of software engineering research [Frakes and Kang 2005]. It aims to reduce development and maintenance efforts and, at the same time, improve software quality due to the use of already designed software units, implemented, validated, and tested [Peters and Pedrycz 2000] [Sommerville 2011]. We observe that database automatic tuning tools share a core of common tasks, even though they might suggest different tuning action types. All self-tuning systems rely on basic tasks such as workload capture, data extraction, SQL parsing, or DBMS catalog access. Hence, this research area could take advantage of software reuse. However, reuse opportunities to support the comparison and evaluation of database self-tuning tools have not yet been systematically explored. Aiming at taking a step towards bridging this gap, this paper describes how we may instantiate a reuse-oriented framework to support the evaluation of self-tuning tools for relational database systems. This framework reduces the effort of building a special- ized database application by identifying a typical common architecture and enabling cus- tomization through well-defined framework hot-spots that may implement specific tuning strategies. In pursuit of this aim, this paper makes the following contributions: 1. A suggested list of reuse-oriented requirements for database self-tuning tools where we discuss possible modeling options and justify our choices; 2. A component-based architecture of a framework to create self-tuning applications for relational databases with its corresponding open-source implementation; 3. Three customized automatic database tuning tools extended from our framework kernel, employing strategies using combinations of different tuning actions (in- dexes, partial indexes, and materialized views) for different RDBMS; 4. An evaluation of how effective our self-tuning tools are and how much they can increase the throughput of a well-known benchmark. Based on our results, we conclude that the framework enabled instantiating useful self-tuning tools empolying different strategies, which significantly reduced query execu- tion costs on different RDMS, with low effort. Hence, we believe that it can serve as a valuable common and extensible testbed for further evolving self-tuning strategies. Our framework is open-source and is available at https://github.com/hidden-for- double-blind-review All data, queries, and selected tuning actions, besides results ob- tained, are available at hidden-for-double-blind-review for experimental reproducibility. The remainder of this paper is organized as follows. Section 2 presents concepts about software reuse and database tuning. In Section 3, we propose a list of reuse-oriented requirements for database self-tuning tools. We discuss possible modeling options and justify our choices. It also puts forward our software framework to support building database self-tuning tools. Section 4 depicts the evaluation process and experimental results for database self-tuning tools built using our framework. Section 5 describes the related work and discusses database self-tuning tools. Finally, Section 6 brings our con- cluding remarks. 2. Background Software reuse is the use of existing software or software knowledge to develop new software. Reusable assets can be either reusable software or software knowledge. It aims to reduce development and maintenance costs and improve software quality due to the use of already designed, implemented, validated and tested software units [Sommerville 2011]. Reusable software components are self-contained, clearly identifiable artifacts that describe or perform specific functions and have clear interfaces, appropriate docu- mentation, and a defined reuse status [Sametinger 1997]. Components are ideally known as software pieces that can be reused in many software systems [Alvaro et al. 2007]. A framework is a reusable application that can be specialized to produce custom applications. Frameworks aim at reusing software units divided according to the require- ments of the final software [Fayad et al. 1999]. Typical characteristics of software frame- works include a reusable, semi-complete application that can be specialized to produce custom applications or can act as an application generator directly related to a specific domain [Fayad and Schmidt 1997]. The points of the flexibility of a framework are called hot-spots, which are typically abstract classes or methods that must be implemented. If one wants to generate an application based on a framework, it is necessary to implement a specific code for each hot-spot. Some features of the framework are not mutable and constitute the framework kernel, also called frozen-spots. Database tuning is the process of making a database application run more quickly. This usually means higher throughput, and it may also mean lower response time for some applications [Shasha and Bonnet 2002]. The process of database tuning is an activity where the Database Administrator (DBA) monitors the database, plans pos- sible tuning actions, evaluates and executes them on the database system, and, again, monitors the database to observe the impact on the workload. Self-tuning tools automate this process by delegating steps performed by the DBA to autonomic mechanisms able to follow algorithms and heuristics to monitor and execute tuning actions. Performance is the main optimization goal of the tuning activity. The literature considers different optimization goals, such as availability, fault tolerance, and resource consumption. In this paper, we present a framework to support developing self-tuning tools that can target any of these optimization opportunities. Several reasons motivate database self-tuning systems: (i) the increasing complex- ity of multi-tenant monolithic applications and services; (ii) the growing complexity of RDBMS’s administration and tuning, which provides hundreds of tuning knobs; (iii) the high cost of ownership for RDBMS-based solution, where hiring experts in system tuning and management is dominant [Chaudhuri and Weikum 2005]. There are many tuning action types defined in the literature. In this work, we focus on the manipulation of three access structures that may achieve better performance for database systems: indexes, partial indexes, and materialized views. We will explore the action of creating these structures with a closer look into multiple DBMSs, exploring our reuse-oriented framework solution. 3. Requirements and Framework Architecture Overview There is a comprehensive amount of literature surrounding
Load more

Recommended publications
  • Oracle Database Vault DBA Administrative Best Practices
    Oracle Database Vault DBA Administrative Best Practices ORACLE WHITE PAPER | MAY 2015 Table of Contents Introduction 2 Database Administration Tasks Summary 3 General Database Administration Tasks 4 Managing Database Initialization Parameters 4 Scheduling Database Jobs 5 Administering Database Users 7 Managing Users and Roles 7 Managing Users using Oracle Enterprise Manager 8 Creating and Modifying Database Objects 8 Database Backup and Recovery 8 Oracle Data Pump 9 Security Best Practices for using Oracle RMAN 11 Flashback Table 11 Managing Database Storage Structures 12 Database Replication 12 Oracle Data Guard 12 Oracle Streams 12 Database Tuning 12 Database Patching and Upgrade 14 Oracle Enterprise Manager 16 Managing Oracle Database Vault 17 Conclusion 20 1 | ORACLE DATABASE VAULT DBA ADMINISTRATIVE BEST PRACTICES Introduction Oracle Database Vault provides powerful security controls for protecting applications and sensitive data. Oracle Database Vault prevents privileged users from accessing application data, restricts ad hoc database changes and enforces controls over how, when and where application data can be accessed. Oracle Database Vault secures existing database environments transparently, eliminating costly and time consuming application changes. With the increased sophistication and number of attacks on data, it is more important than ever to put more security controls inside the database. However, most customers have a small number of DBAs to manage their databases and cannot afford having dedicated people to manage their database security. Database consolidation and improved operational efficiencies make it possible to have even less people to manage the database. Oracle Database Vault controls are flexible and provide security benefits to customers even when they have a single DBA.
    [Show full text]
  • 2 Day + Performance Tuning Guide
    Oracle® Database 2 Day + Performance Tuning Guide 21c F32092-02 August 2021 Oracle Database 2 Day + Performance Tuning Guide, 21c F32092-02 Copyright © 2007, 2021, Oracle and/or its affiliates. Contributors: Glenn Maxey, Rajesh Bhatiya, Lance Ashdown, Immanuel Chan, Debaditya Chatterjee, Maria Colgan, Dinesh Das, Kakali Das, Karl Dias, Mike Feng, Yong Feng, Andrew Holdsworth, Kevin Jernigan, Caroline Johnston, Aneesh Kahndelwal, Sushil Kumar, Sue K. Lee, Herve Lejeune, Ana McCollum, David McDermid, Colin McGregor, Mughees Minhas, Valarie Moore, Deborah Owens, Mark Ramacher, Uri Shaft, Susan Shepard, Janet Stern, Stephen Wexler, Graham Wood, Khaled Yagoub, Hailing Yu, Michael Zampiceni This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S.
    [Show full text]
  • An End-To-End Automatic Cloud Database Tuning System Using Deep Reinforcement Learning
    An End-to-End Automatic Cloud Database Tuning System Using Deep Reinforcement Learning Ji Zhangx, Yu Liux, Ke Zhoux , Guoliang Liz, Zhili Xiaoy, Bin Chengy, Jiashu Xingy, Yangtao Wangx, Tianheng Chengx, Li Liux, Minwei Ranx, and Zekang Lix xWuhan National Laboratory for Optoelectronics, Huazhong University of Science and Technology, China zTsinghua University, China, yTencent Inc., China {jizhang, liu_yu, k.zhou, ytwbruce, vic, lillian_hust, mwran, zekangli}@hust.edu.cn [email protected]; {tomxiao, bencheng, flacroxing}@tencent.com ABSTRACT our model and improves efficiency of online tuning. We con- Configuration tuning is vital to optimize the performance ducted extensive experiments under 6 different workloads of database management system (DBMS). It becomes more on real cloud databases to demonstrate the superiority of tedious and urgent for cloud databases (CDB) due to the di- CDBTune. Experimental results showed that CDBTune had a verse database instances and query workloads, which make good adaptability and significantly outperformed the state- the database administrator (DBA) incompetent. Although of-the-art tuning tools and DBA experts. there are some studies on automatic DBMS configuration tuning, they have several limitations. Firstly, they adopt a 1 INTRODUCTION pipelined learning model but cannot optimize the overall The performance of database management systems (DBMSs) performance in an end-to-end manner. Secondly, they rely relies on hundreds of tunable configuration knobs. Supe- on large-scale high-quality training samples which are hard rior knob settings can improve the performance for DBMSs to obtain. Thirdly, there are a large number of knobs that (e.g., higher throughput and lower latency). However, only a are in continuous space and have unseen dependencies, and few experienced database administrators (DBAs) master the they cannot recommend reasonable configurations in such skills of setting appropriate knob configurations.
    [Show full text]
  • Oracle Performance Tuning Checklist
    Oracle Performance Tuning Checklist Griseous Wayne rear afire. Relaxing Rutger gloze fermentation. Good-natured Renault limb, his retaker wallowers capes sedately. This uses akismet to remove things like someone in sql, and best used in those rows and oracle performance tuning is used inside of system Before being stressed, you know this essentially uses cookies could do not mentioned reduce the nonclustered index fragmentation and oracle performance tuning advisor before purchasing additional encryption of both. Tips and features such features available in other tools to oracle performance tuning checklist. Tuning an Oracle database Use Automatic Workload Repository AWR reports to collect diagnostics data Review essential top-timed events for potential bottlenecks Monitor the excellent for different top SQL statement You separate use an AWR report on this base Make against that the SQL execution plans are optimal. In mind when building it out of oracle performance tuning checklist, dbas will also has been defined in presentation layer of db trace or removed from. Maybe show lazy loaded dataspace will be configured on a fetch them? Create a sql query statements automatically add something about obiee design efforts on file as a performance oracle tuning checklist. Each replicated and performance checklist be ready time as smart scan is. Optimal size values within this? Even more visible, and analytics experts. Do some pain points for last validation report back an performance oracle tuning checklist data, oracle golden gate installation can configure rman backups have. This oracle performance tuning checklist is never used as html does. Performance Tuning Checklist JIRA Performance Tuning Best Practices and.
    [Show full text]
  • Oracle Database 2 Day + Performance Tuning Guide, 10G Release 2 (10.2) B28051-02
    Oracle® Database 2 Day + Performance Tuning Guide 10g Release 2 (10.2) B28051-02 January 2008 Easy, Automatic, and Step-By-Step Performance Tuning Using Oracle Diagnostics Pack, Oracle Database Tuning Pack, and Oracle Enterprise Manager Oracle Database 2 Day + Performance Tuning Guide, 10g Release 2 (10.2) B28051-02 Copyright © 2006, 2008, Oracle. All rights reserved. Primary Author: Immanuel Chan Contributors: Karl Dias, Cecilia Grant, Connie Green, Andrew Holdsworth, Sushil Kumar, Herve Lejeune, Colin McGregor, Mughees Minhas, Valarie Moore, Deborah Owens, Mark Townsend, Graham Wood The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
    [Show full text]
  • Database Performance Study
    Database Performance Study By Francois Charvet Ashish Pande Please do not copy, reproduce or distribute without the explicit consent of the authors. Table of Contents Part A: Findings and Conclusions…………p3 Scope and Methodology……………………………….p4 Database Performance - Background………………….p4 Factors…………………………………………………p5 Performance Monitoring………………………………p6 Solving Performance Issues…………………...............p7 Organizational aspects……………………...................p11 Training………………………………………………..p14 Type of database environments and normalizations…..p14 Part B: Interview Summaries………………p20 Appendices…………………………………...p44 Database Performance Study 2 Part A Findings and Conclusions Database Performance Study 3 Scope and Methodology The authors were contacted by a faculty member to conduct a research project for the IS Board at UMSL. While the original proposal would be to assist in SQL optimization and tuning at Company A1, the scope of such project would be very time-consuming and require specific expertise within the research team. The scope of the current project was therefore revised, and the new project would consist in determining the current standards and practices in the field of SQL and database optimization in a number of companies represented on the board. Conclusions would be based on a series of interviews with Database Administrators (DBA’s) from the different companies, and on current literature about the topic. The first meeting took place 6th February 2003, and interviews were held mainly throughout the spring Semester 2003. Results would be presented in a final paper, and a presentation would also be held at the end of the project. Individual summaries of the interviews conducted with the DBA’s are included in Part B. A representative set of questions used during the interviews is also included.
    [Show full text]
  • Oracle Database Performance Tuning Guide, 11G Release 2 (11.2) E16638-03
    Oracle® Database Performance Tuning Guide 11g Release 2 (11.2) E16638-03 August 2010 Oracle Database Performance Tuning Guide, 11g Release 2 (11.2) E16638-03 Copyright © 2000, 2010, Oracle and/or its affiliates. All rights reserved. Primary Authors: Immanuel Chan, Lance Ashdown Contributors: Aditya Agrawal, Hermann Baer, Vladimir Barriere, Mehul Bastawala, Eric Belden, Pete Belknap, Supiti Buranawatanachoke, Sunil Chakkappen, Maria Colgan, Benoit Dageville, Dinesh Das, Karl Dias, Kurt Engeleiter, Marcus Fallen, Mike Feng, Leonidas Galanis, Ray Glasstone, Prabhaker Gongloor, Kiran Goyal, Cecilia Grant, Connie Dialeris Green, Shivani Gupta, Karl Haas, Bill Hodak, Andrew Holdsworth, Hakan Jacobsson, Shantanu Joshi, Ameet Kini, Sergey Koltakov, Vivekanada Kolla, Paul Lane, Sue K. Lee, Herve Lejeune, Ilya Listvinsky, Bryn Llewellyn, George Lumpkin, Mughees Minhas, Gary Ngai, Mark Ramacher, Yair Sarig, Uri Shaft, Vishwanath Sreeraman, Vinay Srihari, Randy Urbano, Amir Valiani, Venkateshwaran Venkataramani, Yujun Wang, Graham Wood, Khaled Yagoub, Mohamed Zait, Mohamed Ziauddin This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S.
    [Show full text]
  • Database Tuning Progress in a Decade
    J. Basic. Appl. Sci. Res. , 6(11)15-25, 2016 ISSN 2090-4304 © 2016, TextRoad Publication Journal of Basic and Applied Scientific Research www.textroad.com Systematic Mapping: Database Tuning Progress in a Decade 1Saba Luqman, 2Ejaz Ahmed Department of Computer Science National University of Computer and Emerging Sciences, Islamabad, Pakistan Received: September 6, 2016 Accepted: October 29, 2016 ABSTRACT Database tuning is the incremental process of tuning database and database applications to run more rapidly. With the help of tuning, transactions are executed efficiently in minimum time. A large number of published research articles are presenting database tuning but there is a deficiency of systematic research. Our focus is to provide a critical review of the nature of the systematic mapping which means performing survey on existing research of database tuning in order to identify useful approaches and map research characteristics. For the last many years, some researchers work has been carried out with different classification tuning schemes. Our results show unique and distinct percentiles of research, performed in the study of publications such as book chapters, conferences, journals, thesis reports and research articles related to database tuning in the last one decade. According to results of our systematic mapping, we find that how a significant tuning related research in terms of validation and evaluation has required? KEYWORDS : Database Tuning, Systematic Mapping, Classification, Evaluation, Threats to validity, Research Focus 1. INTRODUCTION Recent developments in science and technology depend on access of very large data in a shortest response time. This has created an immense opportunity for transactional data research to play an essential role in wide range of applications for database systems such as country's population databases, banks transactional systems, hospitals databases, and databases for macro scale knowledge discovery.
    [Show full text]
  • Autoadmin: Self-Tuning Database Systems Technology
    AutoAdmin: Self-Tuning Database Systems Technology Sanjay Agrawal, Nicolas Bruno, Surajit Chaudhuri, Vivek Narasayya Microsoft Research 1 Introduction The AutoAdmin research project was launched in the Fall of 1996 in Microsoft Research with the goal of making database systems significantly more self-tuning. Initially, we focused on automating the physical design for relational databases. Our research effort led to successful incorporation of our tuning technology in Microsoft SQL Server and was subsequently also followed by similar functionality in other relational DBMS products. In 1998, we developed the concept of self-tuning histograms, which remains an active research topic. We also attempted to deepen our understanding of monitoring infrastructure in the relational DBMS context as this is one of the core foundations of the “monitor-diagnose-tune” paradigm needed for making relational DBMS self- tuning. This article gives an overview of our progress in the above three areas – physical database design, self-tuning histograms and monitoring infrastructure. 2 Physical Database Design Tuning One great virtue of the relational data model is its data independence, which allows the application developer to program without worrying about the underlying access paths. However, the performance of a database system crucially depends on the physical database design. Yet, unlike widespread use of commercial tools for logi- cal design, there was little support for physical database design for relational databases when we started the AutoAdmin project. Our first challenge was to understand the physical design problem precisely. There were several key architectural elements in our approach. Use of Workload: The choice of the physical design depends on the usage profile of the server, so we use a representative workload (defined as a set of SQL DML statements such as SELECT, INSERT, DELETE and UPDATE statements), as a key input to the physical design selection problem.
    [Show full text]
  • DB2 II: Performance Monitoring, Tuning and Capacity Planning Guide
    Front cover DB2 II: Performance Monitoring, Tuning and Capacity Planning Guide DB2 Information Integrator V8.2 performance drivers and best practices Performance problem determination scenarios Capacity planning Nagraj Alur Miriam Goodwin Hajime Kawada Roger Midgette DB Shenoy Ron Warley ibm.com/redbooks International Technical Support Organization DB2 II: Performance Monitoring, Tuning and Capacity Planning Guide November 2004 SG24-7073-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xv. First Edition (November 2004) This edition applies to Version 8, Release 2 of DB2 Information Integrator (product number 5724-C74). © Copyright International Business Machines Corporation 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . vii Tables . ix Examples. xi Notices . xv Trademarks . xvi Preface . xvii The team that wrote this redbook. xvii Become a published author . xx Comments welcome. xx Chapter 1. DB2 Information Integrator architecture overview . 1 1.1 Introduction . 2 1.2 Current business trends . 2 1.2.1 From on demand to grid computing . 3 1.2.2 From grid computing to data federation . 4 1.2.3 From data federation to information integration . 5 1.3 IBM’s DB2 Information Integration overview . 6 1.3.1 Data consolidation or placement. 8 1.3.2 Distributed access (federation) . 9 1.3.3 DB2 Information Integrator products . 9 1.4 DB2 Information Integrator V8.2 . 11 1.4.1 DB2 II V8.2 overview. 11 1.4.2 DB2 II components . 15 1.4.3 Configuring the federated system .
    [Show full text]
  • A New Frontier for Database Tuning and Physical Design
    Database Virtualization: A New Frontier for Database Tuning and Physical Design Ahmed A. Soror Ashraf Aboulnaga Kenneth Salem David R. Cheriton School of Computer Science University of Waterloo {aakssoro, ashraf, kmsalem}@cs.uwaterloo.ca Abstract researchers. In this paper, we focus on the second question, Resource virtualization is currently being employed at and we present preliminary results of our work towards ad- all levels of the IT infrastructure to improve provisioning dressing it. and manageability, with the goal of reducing total cost of ownership. This means that database systems will increas- 1.1. Why Virtualization? ingly be run in virtualized environments, inside virtual ma- The basic idea behind resource virtualization is to de- chines. This has many benefits, but it also introduces new couple the user’s perception of hardware and software re- tuning and physical design problems that are of interest to sources from the actual implementation of these resources. the database research community. In this paper, we dis- Resource virtualization technologies add a flexible and pro- cuss how virtualization can benefit database systems, and grammable layer of software between “applications” (in our we present the tuning problems it introduces, which relate case database systems) and the resources used by these ap- to setting the new “tuning knobs” that control resource al- plications. This layer of software maps the virtual resources location to virtual machines in the virtualized environment. perceived by applications to real physical resources. By We present a formulation of the virtualization design prob- managing this mapping from virtual resources to physical lem, which focuses on setting resource allocation levels for resources and changing it as needed, the virtualization layer different database workloads statically at deployment and can be used to transparently allow multiple applications to configuration time.
    [Show full text]
  • Evaluation of Sql Performance Tuning Features in Oracle Database Software Katarzyna Marta Dobies Regis University
    Regis University ePublications at Regis University All Regis University Theses Summer 2013 Evaluation of Sql Performance Tuning Features in Oracle Database Software Katarzyna Marta Dobies Regis University Follow this and additional works at: https://epublications.regis.edu/theses Part of the Computer Sciences Commons Recommended Citation Dobies, Katarzyna Marta, "Evaluation of Sql Performance Tuning Features in Oracle Database Software" (2013). All Regis University Theses. 220. https://epublications.regis.edu/theses/220 This Thesis - Open Access is brought to you for free and open access by ePublications at Regis University. It has been accepted for inclusion in All Regis University Theses by an authorized administrator of ePublications at Regis University. For more information, please contact [email protected]. Regis University College for Professional Studies Graduate Programs Final Project/Thesis Disclaimer Use of the materials available in the Regis University Thesis Collection ("Collection”) is limited and restricted to those users who agree to comply with the following terms of use. Regis University reserves the right to deny access to the Collection to any person who violates these terms of use or who seeks to or does alter, avoid or supersede the functional conditions, restrictions and limitations of the Collection. The site may be used only for lawful purposes. The user is solely responsible for knowing and adhering to any and all applicable laws, rules, and regulations relating or pertaining to use of the Collection. All content in this Collection is owned by and subject to the exclusive control of Regis University and the authors of the materials. It is available only for research purposes and may not be used in violation of copyright laws or for unlawful purposes.
    [Show full text]