文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > 工程科技 > 能源/化工 > Survey of techniques used to reduce the Semantic Gap between ....doc
侵权投诉

Survey of techniques used to reduce the Semantic Gap between ....doc

——均是精品资料,值得下载!下的越多,我越开心了。哈哈

Survey of techniques used to reduce the Semantic Gap between Database Management Systems and Storage Subsystems

1. Introduction

One of the most important modules of any database management system is the storage manager module. This module essentially controls the way the data is allocated, accessed, and stored on storage devices. Storage subsystems are typically virtualized for the purposes of consolidation, easy of management, reducing interdependence, etc. Due to this virtualization now the database storage managers neither have a strict control over the physical layout of data nor are they aware of the internal characteristics of storage subsystems, and apply some coarse rules of thumb to optimize its access. On the other hand, storage subsystems do not have semantic knowledge of the data that they are storing, again relying on their own rules of thumb to manage such workload-dependent tasks as pre-fetching, caching, and data layout. The end result is both sides are working blindly to optimize their performance without not knowing what other side is doing. Various studies [1][2] emphasize the importance reducing information gap between applications and underlying storage devices. Over the years, various techniques have been developed to reduce the semantic gap between database management systems and storage systems. In this project we plan to survey various approaches used by researchers or implementers in order to reduce this semantic gap.

The idea of placing intelligence in storage systems to help database operation was explored extensively in the context of database machines in late 1970s and late 1980s. Database machines can be classified into four categories depending on disk processing

[8]:

1. Processor per head: DBC, SURE

2. Processor per track: CAFS, RARES, RAP, CASSM

3. Processor per disk: SURE

4. Multi-processor cache: DIRECT, RDBM, DBMAC, INFOPLEX, RAP.2

In all of the architectures, there was a central processor which pushed simple database operations (e.g., scan) closer to disk, and achieved a dramatic performance improvement for these operations. The main counter-arguments are summarized by Boral and Dewitt

[11]. First, most database machine use special-purpose hardware, such as associative disks, associative CCD devices, and magnetic bubble memory which increased the design time and cost of these machines. Again, the performance gain was not enough to justify the additional cost incurred by these hardwares. Second, although the performance was impressive for scan operations, but for the complex database operations, such as sorts and joins did not provide significant benefits. Third, the performance offered by database machines can be easily achievable by smart indexing techniques. Fourth, CPU processing speed was improving much faster than the disk transfer rates improve, so CPU was sitting idle. Fifth, the communication overhead between processing elements were high. Finally, database vendors did not agree to rewrite their legacy code base to take advantage of features offered by these new hardware.

上一页第2页

你可能喜欢

热门文档

相关文档

站点地图 | 文档上传 | 侵权投诉 | 手机版
本站所有资源均来自互联网,本站只负责收集和整理,均不承担任何法律责任,如有侵权等其它行为请联系我们.
文档下载 Copyright 2013 doc.guandang.net All Rights Reserved.  -  email