<!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 Analytical Query Processing on Disaggregated Hardware</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andreas Geyer</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Supervised by: Wolfgang Lehner Dresden University of Technology (TU Dresden)</institution>
          ,
          <addr-line>Dresden, 01069</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In a world of ever-growing amounts of data, hardware-scalability and energy-eficiency become more important with every year. Traditional scale-up and scale-out database management systems (DBMS) struggle to scale well with their growing analytical workloads. Due to this, the emerging technology of disaggregated hardware becomes more and more popular. However, there is no free ride and specific challenges arise. In my PhD topic, I want (i) to look into these challenges for analytical query workloads on disaggregated hardware and (ii) to provide appropriate solutions. First initial results concerning data movement are promising and show the potential of adapted solutions.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;RDMA</kwd>
        <kwd>Disaggregated Memory</kwd>
        <kwd>Disaggregated Hardware</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        theless and as we focus on analytical query processing
(OLAP) as a prime representative for data-intensive
workWith the ongoing shift to a data-driven world in almost loads, the eficient data exchange between MUs and CUs
all application domains, the management and analyt- is a major challenge.
ics of data gain importance. However, the demand for To minimize the amount of data to be transferred
computing power as well as memory capacities is also between CUs and MUs, solution approaches such as
growing to enable eficient data analytics over an ever- function-to-data (operator push-down) like in [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] or
nearincreasing amount of data. To satisfy these ever-growing memory computing schemes [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] are heavily applied.
hardware demands in a scalable and flexible way, the However, these approaches lead to the fact that they
emerging technology of hardware disaggregation is con- cannot scale the computations, due to limited resources,
sidered the "next big thing" [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Hardware disaggregation as we would be able to achieve it by the general
decompois an approach that decomposes general-purpose mono- sition of CUs and MUs. Thus, they only provide limited
lithic servers into separated, network-attached resource applicability. To overcome that shortcoming, we focus
pools, each of which can be built, managed, and scaled on solutions regarding the data-to-function schema by
independently. This hardware disaggregation ofers var- making the data transfer explicit as first-class citizen in
ious valuable possibilities such as (i) fast, fine-grained such an architecture. With this explicit treatment, we are
scalability depending on individual workloads, (ii) en- able to synchronize the assignments of computations to
ergy proportionality, or (iii) resource sharing capabilities. CUs and the necessary data exchange in a scalable and
However, there is no free ride and specific challenges lfexible way. This synchronisation includes several
asarise. In my thesis, I want to focus on analytical query pects such as (i) diferent computations on the same data
processing on disaggregated memory systems and solv- across diferent queries can be grouped at one CU, so that
ing the specific challenges in that scope. the necessary data must be transferred only to this CU,
      </p>
      <p>
        The foundation of our work is an appropriate system (ii) data transfer can be done in an asynchronous way to
architecture, similar to the one from [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], with dedicated interleave it with the computation to hide latency, or (iii)
units for computation and memory. These are named preparing data during transfer for subsequent processing
Compute Units (CUs) and Memory Units (MUs). CUs and at the CU by e.g., adapting the data layout.
MUs are explicitly decomposed and connected via a net- While still being in an early stage of my PhD thesis
work. With modern network technologies like Com- (1st year), we argue that this research direction has high
pute Express Link (CXL) or Remote Direct Memory Ac- potential. To show that, the remainder of this paper is
cess (RDMA) over InfiniBand (IB) , there are already high- organized as follows: In Section 2, we discuss a
selecthroughput, low-latency interconnects available. Never- tion of already existing solutions. Then, we give a more
detailed view of our current approach including some
preliminary results in Section 3. Finally, we conclude
with a summary and outlook in Section 4.
      </p>
      <p>Published in the Workshop Proceedings of the EDBT/ICDT 2023 Joint
Conference (March 28-March 31, 2023, Ioannina, Greece)
$ Andreas.Geyer@tu-dresden.de (A. Geyer)</p>
      <p>© 2023 Copyright for this paper by its authors. Use permitted under Creative
CPWrEooUrckReshdoinpgs IhStpN:/c1e6u1r3-w-0s.o7r3g CCoEmmUoRns LWiceonsrekAstthribouptionP4r.0oIncteerenadtiionnagl s(CC(CBYE4U.0)R.-WS.org)
Q1
Q2
Q3</p>
      <sec id="sec-1-1">
        <title>Query</title>
      </sec>
      <sec id="sec-1-2">
        <title>Batcher</title>
      </sec>
      <sec id="sec-1-3">
        <title>Query</title>
      </sec>
      <sec id="sec-1-4">
        <title>Batch</title>
      </sec>
      <sec id="sec-1-5">
        <title>Query</title>
      </sec>
      <sec id="sec-1-6">
        <title>Optimizer</title>
      </sec>
      <sec id="sec-1-7">
        <title>Optimizer Goals</title>
      </sec>
      <sec id="sec-1-8">
        <title>Pipelines</title>
      </sec>
      <sec id="sec-1-9">
        <title>Pipeline</title>
      </sec>
      <sec id="sec-1-10">
        <title>Grouper</title>
        <p>PU
PU
PU
PU</p>
      </sec>
      <sec id="sec-1-11">
        <title>Memory PU PU</title>
      </sec>
      <sec id="sec-1-12">
        <title>Data</title>
      </sec>
      <sec id="sec-1-13">
        <title>Transfer</title>
      </sec>
      <sec id="sec-1-14">
        <title>Manager</title>
      </sec>
      <sec id="sec-1-15">
        <title>Scheduler</title>
      </sec>
      <sec id="sec-1-16">
        <title>Parameter</title>
      </sec>
      <sec id="sec-1-17">
        <title>Server</title>
      </sec>
      <sec id="sec-1-18">
        <title>Data</title>
      </sec>
      <sec id="sec-1-19">
        <title>Transfer</title>
      </sec>
      <sec id="sec-1-20">
        <title>Pipeline Group Executor</title>
        <p>MUs
PU
PU
PU</p>
      </sec>
      <sec id="sec-1-21">
        <title>Memory</title>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        to the principle of scan sharing [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>
        On the one hand, recent work also has just shown the
Disaggregated hardware revolutionizes the design and ar- viability of CXL-attached main memory [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. Our
prochitecture of modern database systems and thus database totype implementation is currently based on one-sided
researchers have just started to investigate the potential RDMA verbs, but our memory access layer is already
implications of such a novel hardware model. For ex- prepared to also work with memory via CXL as soon as
ample, [
        <xref ref-type="bibr" rid="ref1 ref3 ref5 ref6">1, 3, 5, 6</xref>
        ] discuss the general impact and among we have access to corresponding hardware. On the other
other things infer a new architecture as well as database hand, DFI [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] is a framework to eficiently exploit
highprimitives. We fully agree that disaggregation leads to speed networks, such as IB. They show that adding an
an alteration of traditional query handling. abstraction layer on top of RDMA verbs does not impose
      </p>
      <p>
        The authors of [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] introduce an approach for dis- a significant performance degradation. However, their
tributed shared-memory databases (DSM-DB). Their sys- experiments are tailored towards tuple-based data
protem architecture is similar to ours as we will describe cessing, whereas we focus on column- or batch-oriented
in Section 3.1, but it focuses on OLTP workloads, while data transfer.
we focus on OLAP. However, it will be interesting to
compare this similar strategy to our own in the future.
      </p>
      <p>
        There are already system prototypes like LegoOS [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], 3. Our Contributions
PolarDB [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], Teleport [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], Farview [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and more emerge.
      </p>
      <p>
        LegoOS tackles the operating system side for steering The focus of my thesis lies on pipeline execution, as
and controlling the actual hardware components, which state-of-the-art execution model for analytical query
prois an extremely interesting feature for elasticity, but or- cessing (OLAP), introduced in [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], on disaggregated
thogonal to our proposed processing model. PolarDB – hardware. The challenges coming with it arise from the
very similar to our architectural blueprint – plans with main OLAP properties. First, ○ 1 it is necessary to access
separate compute nodes but attributes the remainder of a lot of data for these workloads, which traditionally
rethe resources to individual pools. Contrarily, we argue sults in scans of whole columns or even tables. Second,
that dedicated units with individual compute resources ○ 2 a lot of queries are executed simultaneously and most
as in our system architecture yield benefits, for example, probably access the same data multiple times. Therefore,
the preservation of the opportunity for operator push- data transfer is a potential bottleneck and thus, an
inteldown. In Teleport, the authors observe that the high ligent and optimized data transfer is crucial. The idea of
network latency of ‘remote’ accesses is impacting data- making the data transfer explicit allows us to tune the
intensive systems and thus opt for compute or operator pipeline execution in a way that the latency through
netpush-down. Approaches with network-attached memory work communication is nearly negligible. Additionally,
(NAM) [
        <xref ref-type="bibr" rid="ref10 ref9">9, 10</xref>
        ] are promising but lack the possibility of we argue that this allows us to utilize the given
flexibiloperator push-down, similar to Teleport. Farview’s on- ity that disaggregated hardware ofers when it comes to
demand provisioning of compute nodes paired with the resource management.
      </p>
      <p>FPGA-controlled storage serves as a general inspiration
for our work. However, Farview considers the execution 3.1. General System Architecture
of individual pipelines, which is contrary to our
processing model, which is based on shared data access similar
As there is a wide variety of possibilities to structure a
system based on disaggregated hardware, we start with
9
8
]7
s
[
e6
m
iT5
ing4
s
s
3
e
c
o
r
P2
1
0 0/3</p>
      <p>Local
NUMA
1/3</p>
      <p>Overlap
Chunked Pipeline
Chunked Prefetch
2/3</p>
      <p>3/3
Column Pipeline
Column Prefetch</p>
      <p>Local
NUMA
1/3</p>
      <p>Overlap
Chunked Pipeline
Chunked Prefetch
2/3</p>
      <p>
        3/3
Column Pipeline
Column Prefetch
(a) 4 pipelines executed sequentially with 4 threads for each
pipeline
(b) 4 pipelines executed fully parallel with 1 thread for each
pipeline
our anticipated system design as introduced in our CIDR responsible for the sending process (one-sided IB verb
2023 publication [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Figure 1 depicts a related sketch. RDMA_WRITE) and writes to the RB of the remote
sysAs already introduced, we separate our system into CUs tem. Since we make the bufers exclusive for each
CU-toand MUs based on their respective task. While MUs fea- MU connection, we can prevent conflicts of concurrent
ture high memory capacities (DRAM, NVRAM, ...) with a write processes to the same bufer.
limited amount of compute resources, CUs provide a high Through extensive evaluation of diferent
configuraamount of compute resources with a limited main mem- tions of our initial communication layer, we found a
ory capacity. Thus, CUs are merely responsible for exe- multi-bufer approach as best fitting. This approach
imcuting queries, managing the lifecycle of intermediates plies that there can be multiple SBs and RBs on each
and feeding results to the clients. Apart from operator system. Thereby, we can hide the latency introduced by
pushdown, base data has to be fetched from MUs. the consumption of the content from the RB and write
      </p>
      <p>This architecture works with one-to-one connections continuously to other free bufers. With this approach,
for CU and MU, as long as the MU holds all relevant we found that already a configuration with one SB and
data. However, the idea is to have an N-to-M connection two remote RBs has big benefits in comparison to a
singlebetween CUs and MUs. The connections are realised bufer approach. Using multiple threads on each node
through a high-throughput, low-latency interconnect also improves the performance further.
like IB or CXL, for instance. This communication layer is continuously developed</p>
      <p>As this architecture is already realizable with commod- to further allow a multitude of other interconnect
techity systems, we argue that it allows transferring knowl- nologies additional to RDMA over IB.
edge from the well-known system architectures to the
new one based on disaggregated hardware. In the ab- 3.3. Pipeline Group Concept
sence of real disaggregated hardware, we emulate both
CU and MU with standard monolithic server systems
directly connected through IB. As soon as disaggregated
hardware is available for us, we will apply our proposed
architecture and components to it.</p>
      <p>Based on the implementation of the communication layer,
the pipeline-based processing model is re-evaluated on
the given system architecture. As base tables are assumed
to be in-memory on the MU, when answering the query,
the data needs to be transferred from the MU to the CU.
3.2. Communication Layer The naïve implementation based on the state-of-the-art
pipeline-execution model shows that the processing time
Even with fast interconnects, the network is prone to for a pipeline is mainly dominated by the data transfer.
be the bottleneck of the whole architecture, especially Following these results and tackling properties ○ 1 and
in data heavy OLAP scenarios. Thus, we started our ○ 2 , the main target is to reduce the amount of
transresearch by developing a flexible communication layer ferred data and interleave the communication with the
based on RDMA over IB, which is well prepared to in- computation. Thus, we propose an approach of
groupcorporate CXL as soon as we get access to the respec- ing pipelines with similar or the same data-needs into
tive hardware. Following the communication scheme of pipeline-groups. This grouping allows us to prevent
reRDMA there are reserved bufers on each system. We dundant data transfer.
implemented this by a separation into Receive Bufer (RB) Figure 2 depicts two experiments to highlight the
benand Send Bufer (SB) . As the name suggests, the SB is efits of our pipeline-group approach. Both graphs show
the processing time for the execution of 4 simple pipelines
depending on the amount of overlap within their
dataneed. For these experiments Local means all data is
located in-memory attached to the working CPU, NUMA
that there is a NUMA-hop between the memory and
the CPU, Chunked that the data is transferred over the
network in smaller pieces and Column that whole data
columns are transferred at once. In Figure 2a, the more
traditional approach of executing each pipeline with full
resources one after the other is displayed. Orthogonal to
this, Figure 2b shows the fully parallel execution of the
same four pipelines. It is visible, that a higher overlap
in the data-need reduces the processing time of the four
pipelines tremendously in both cases. However, with full
parallelism, it is possible to nearly match the performance
of the NUMA-curve, while the traditional approach does
not perform that well. With these experiments, we argue
that pipeline groups ofer the potential to nearly
eliminate the latency introduced by network communication.</p>
      <p>
        This work has been submitted to CIDR 2023 and was
accepted for publication [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
3.4. Resource Adaption
One of the key aspects of the pipeline group is also that it
allows utilisation of the given flexibility of disaggregated
hardware by scaling the resources individually with the
workload. Several of the blue components of Figure 1
ofer dimensions to exploit this flexibility. The shown
Pipeline Group Executor is capable of managing the
resource allocation in the best fitting way. Thus, it can
for example distribute the workload across multiple CUs
to prevent network-bottlenecks or move the workload
to a CU closer to the data-holding MU. With diferent
scheduling strategies, it is possible to determine how
many resources are needed. Hence, for example,
scenarios, where there is a budget involved can greatly benefit
from our approach as resources (CPU cores, RAM, etc.),
are allocated just when they are needed and released
after the work is done. Additionally, when we integrate
some form of operator push-down, we can react nearly
immediately on the side of the MU to the increased
workload. More CPU power can be allocated to work on this
operator, without impact on the other connections of the
MU. However, even though we already have a proof of
concept for our pipeline group approach, most of these
components are still up for development.
      </p>
    </sec>
    <sec id="sec-3">
      <title>4. Conclusion and Future Work</title>
      <p>We outlined the advantages and challenges of DBMS on
disaggregated hardware, gave a brief overview of the
existing solutions and touched on why we think they are
not suficient to solve the outlined challenges completely.
Additionally, our described approach of pipeline group
execution showed some results of our previous work, to
prove that the concept is capable of solving the challenges
of DBMS on disaggregated hardware as well as utilizing
its flexibility and other advantages.</p>
      <p>To research the topic of a DBMS processing model
that makes the best use of the opportunities and finds
solutions to the introduced challenges of disaggregated
hardware will be one of the key topics of my PhD thesis.
Thus, we will continue to develop our introduced pipeline
group approach.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , et al.,
          <article-title>Rethinking data management systems for disaggregated data centers</article-title>
          ,
          <source>in: CIDR</source>
          ,
          <year>2020</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>R.</given-names>
            <surname>Wang</surname>
          </string-name>
          , et al.,
          <article-title>The case for distributed sharedmemory databases with rdma-enabled memory disaggregation</article-title>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>D.</given-names>
            <surname>Korolija</surname>
          </string-name>
          , et al.,
          <article-title>Farview: Disaggregated memory with operator of-loading for database engines</article-title>
          ,
          <source>in: CIDR</source>
          ,
          <year>2022</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>G.</given-names>
            <surname>Singh</surname>
          </string-name>
          , et al.,
          <article-title>Near-memory computing: Past, present, and future</article-title>
          , CoRR abs/
          <year>1908</year>
          .02640 (
          <year>2019</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , et al.,
          <article-title>Understanding the efect of data center resource disaggregation on production dbmss</article-title>
          ,
          <source>Proc. VLDB Endow</source>
          .
          <volume>13</volume>
          (
          <year>2020</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Q.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , et al.,
          <article-title>Optimizing data-intensive systems in disaggregated data centers with teleport</article-title>
          ,
          <source>in: SIGMOD</source>
          ,
          <year>2022</year>
          , p.
          <fpage>1345</fpage>
          -
          <lpage>1359</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Shan</surname>
          </string-name>
          , et al.,
          <article-title>LegoOS: A disseminated, distributed OS for hardware resource disaggregation</article-title>
          ,
          <source>in: USENIX ATC</source>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>W.</given-names>
            <surname>Cao</surname>
          </string-name>
          , et al.,
          <article-title>Polardb serverless: A cloud native database for disaggregated data centers</article-title>
          ,
          <source>in: SIGMOD</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>2477</fpage>
          -
          <lpage>2489</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>C.</given-names>
            <surname>Binnig</surname>
          </string-name>
          , et al.,
          <article-title>The end of slow networks: It's time for a redesign</article-title>
          ,
          <source>CoRR abs/1504</source>
          .01048 (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>E.</given-names>
            <surname>Zamanian</surname>
          </string-name>
          , et al.,
          <article-title>The end of a myth: Distributed transactions can scale</article-title>
          ,
          <source>Proc. VLDB Endow</source>
          .
          <volume>10</volume>
          (
          <year>2017</year>
          )
          <fpage>685</fpage>
          -
          <lpage>696</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>L.</given-names>
            <surname>Qiao</surname>
          </string-name>
          , et al.,
          <article-title>Main-memory scan sharing for multicore cpus</article-title>
          ,
          <source>PVLDB</source>
          <volume>1</volume>
          (
          <year>2008</year>
          )
          <fpage>610</fpage>
          -
          <lpage>621</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>M.</given-names>
            <surname>Ahn</surname>
          </string-name>
          , et al.,
          <string-name>
            <surname>Enabling</surname>
            <given-names>CXL</given-names>
          </string-name>
          <article-title>memory expansion for in-memory database management systems</article-title>
          , in: DaMoN,
          <year>2022</year>
          , pp.
          <volume>8</volume>
          :
          <fpage>1</fpage>
          -
          <issue>8</issue>
          :
          <fpage>5</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>L.</given-names>
            <surname>Thostrup</surname>
          </string-name>
          , et al.,
          <article-title>DFI: the data flow interface for high-speed networks</article-title>
          ,
          <source>in: SIGMOD</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>1825</fpage>
          -
          <lpage>1837</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>V.</given-names>
            <surname>Leis</surname>
          </string-name>
          , et al.,
          <article-title>Morsel-driven parallelism: a numaaware query evaluation framework for the manycore age</article-title>
          ,
          <source>in: SIGMOD</source>
          ,
          <year>2014</year>
          , pp.
          <fpage>743</fpage>
          -
          <lpage>754</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>A.</given-names>
            <surname>Geyer</surname>
          </string-name>
          , et al.,
          <article-title>Pipeline group optimization on disaggregated systems</article-title>
          , in: CIDR,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>