2014
DOI: 10.1007/978-3-662-45761-0_1
|View full text |Cite
|
Sign up to set email alerts
|

GPU-Accelerated Database Systems: Survey and Open Challenges

Abstract: Abstract. The vast amount of processing power and memory bandwidth provided by modern graphics cards make them an interesting platform for data-intensive applications. Unsurprisingly, the database research community identified GPUs as effective co-processors for data processing several years ago. In the past years, there were many approaches to make use of GPUs at different levels of a database system. In this paper, we explore the design space of GPU-accelerated database management systems. Based on this surv… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
36
0
1

Year Published

2015
2015
2021
2021

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 33 publications
(37 citation statements)
references
References 45 publications
0
36
0
1
Order By: Relevance
“…Due to a fixed set of operations supported by the pipeline, it often resulted in overly complex implementations to work around the restrictions. With the advent of more flexible GPGPU interfaces, there have been several full fledged GPU-accelerated RDBMSs [8,36]. MapD [36] accelerates SQL queries by compiling them to native GPU code and leveraging GPU parallelism.…”
Section: Related Workmentioning
confidence: 99%
“…Due to a fixed set of operations supported by the pipeline, it often resulted in overly complex implementations to work around the restrictions. With the advent of more flexible GPGPU interfaces, there have been several full fledged GPU-accelerated RDBMSs [8,36]. MapD [36] accelerates SQL queries by compiling them to native GPU code and leveraging GPU parallelism.…”
Section: Related Workmentioning
confidence: 99%
“…In the CPU world this is a key feature of Actian Vector [24] (although more for the reason of fitting data in the CPU's cache). With regard to GPU-utilizing query processing frameworks, Virginian [4,3] has employed it, but a more in-depth exploration of its merit and a case for its significance is the recent [13]. Considering our own results, even rough chunks of size, say, 1MB-4MB should already cut most of the initial idle period of the GPU waiting for data to arrive with nothing to work on.…”
Section: Discussion and Further Performance Enhancementmentioning
confidence: 99%
“…by denormalization). Most work surveyed in [4] falls into one of those categories (and there's GPU-DB [23], which uses a di erent benchmark -SSB rather than TPC-H). The design of these various frameworks is interesting to compare with, however, as some of them exhibit desirable features missing in this work (and vice-versa); unfortunately, space constraints preclude this.…”
Section: Comparison With Other Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Ideally, the estimator Listing 1: Adaptively adjusting the bandwidth. foreach query Ω: 6 Computep H (Ω) according to (2). 7 Run query Ω.…”
Section: Self-tuning Kde Modelsmentioning
confidence: 99%