<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Optimizing database architecture for machine architecture: is there still hope?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Peter Boncz</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>CWI p.boncz@cwi.nl</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Extended Abstract</string-name>
        </contrib>
      </contrib-group>
      <pub-date>
        <year>2013</year>
      </pub-date>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>In the keynote, I will give some examples of how computer
architecture has strongly evolved in the past decennia and
how this in uences the performance, and therefore the
design, of algorithms and data structure for data management.
One the one hand, these changes in hardware architecture
have caused the (continuing) need for new data management
research. i.e. hardware-conscious database research. Here,
I will draw examples from hardware-conscious research
performed on the CWI systems MonetDB and Vectorwise.</p>
      <p>This diversi cation trend in computer architectural
characteristics of the various solutions in the market seems to
be intensifying. This is seen in quite di erent architectural
options, such as CPU vs GPU vs FPGA, but also even
restricting oneself to just CPUs there seems to be increasing
design variation in architecture and platform behavior. This
poses a challenge to hardware-conscious database research.</p>
      <p>In particular, there is the all too present danger to
overoptimize of one particular architecture; or to propose
techniques that will have only a very short span of utility. The
question thus is not only to nd speci c ways to optimize
for certain hardware features, but do so in a way that works
across the full spectrum of architectural, i.e. robust
techniques.</p>
      <p>I will close the talk by recent work at CWI and Vectorwise
on robustness of query evaluator performance, describing a
project called "Micro-Adaptivity" where database systems
are made self-adaptive and react immediately to observed
performance, self-optimizing to the combination of current
query workload, observed data distributions, and hardware
characteristics.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>