<!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>
      <journal-title-group>
        <journal-title>Symposium on Software Performance, November</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Automated Benchmarking of Cloud-Hosted DBMS With benchANT</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daniel Seybold</string-name>
          <email>daniel.seybold@uni-ulm.de</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jörg Domaschka</string-name>
          <email>joerg.domaschka@uni-ulm.de</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>DBMS, Cloud, Performance, Scalability, Benchmarking-as-a-Service</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>AWS</institution>
          ,
          <addr-line>Azure, IONOS and Telekom</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>MySQL</institution>
          ,
          <addr-line>PostgreSQL, ArangoDB, Apache Cassandra, Couchbase, MongoDB and CockroachDB</addr-line>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Ulm University, Institute of Information Resource Management Albert-Einstein-Allee 43</institution>
          ,
          <addr-line>89077, Ulm</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Yahoo Cloud Serving Benchmark</institution>
          ,
          <addr-line>YCSB</addr-line>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2021</year>
      </pub-date>
      <volume>0</volume>
      <fpage>9</fpage>
      <lpage>10</lpage>
      <abstract>
        <p>promising a set of non-functional features that are key requirements for each data-intensive application: high performance, horizontal scalability, elasticity and high-availability [4]. In order to take full advantage of these non-functional features, the operation of DBMSs is moving towards elastic infrastructures such as the cloud. Cloud computing enables scalability and elasticity on the resource level. Therefore, the storage backend of data-intensive applications is commonly implemented by distributed DBMSs operated on cloud resources [5].</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>https://www.uni-ulm.de/in/omi/institut/persons/daniel-seybold/ (D. Seybold);</p>
      <p>© 2021 Copyright for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).
CEUR
Workshop
Proceedings
for the non-functional features performance, scalability, elasticity and availability.</p>
      <p>On a technical level, the benchANT platform builds upon our research prototype Mowgli [10],
Kaa [13] and King Louie [14]. Mowgli provides a novel DBMS evaluation framework, supporting
the design and automated execution of performance and scalability evaluation processes. Mowgli
manages cloud resources, DBMS deployment, workload execution and result processing based
on evaluation scenarios, which expose configurable domain-specific parameters. The Kaa
framework [13] automates the DBMS elasticity evaluation process by enabling DBMS and
workload adaptations. The King Louie framework [14] builds upon these features and enables
availability evaluations by providing an extensive failure injection framework.</p>
      <p>benchANT lifts these research results into an enterprise grade BaaS platform with an
easyto-use benchmark configurator. In its current state, benchANT enables the configuration and
automated execution from 7 major RDBMS, NoSQL and NewSQL DBMS2 with DBMS-specific
runtime configurations such as cluster size, replication factor or consistency settings; 4 public
cloud providers3 with over 700 diferent VM flavours and 1 benchmark 4 with 5 workload
configurations. The evaluation results are automatically processed by the benchANT platform
and presented in a result dashboard. The result processing uses the raw DBMS benchmark
metrics throughput and latency to generate higher-level metrics such as the scalability factor [10]
or unified metrics over the dimensions performance, costs and availability [ 15].</p>
      <p>In this talk, we provide an overview how these research results are incorporated into the novel
BaaS concept and demonstrate in a live walk-through how benchANT supports practitioners
and researchers to address performance challenges such as:
• Which cloud provider and which VM flavour provides the best performance/cost ratio for
a 3 node MongoDB cluster?
• Will new DBMS releases always increase the the performance?
• Is there a significant throughput and latency diference between MongoDB, Cassandra
and Couchbase for an IoT workload?</p>
      <p>R. Ramakrishnan, V. Markl, C. Olston, B. C. Ooi, C. Ré, D. Suciu, M. Stonebraker, T. Walter,
J. Widom, The beckman report on database research, Commun. ACM 59 (2016) 92–99.</p>
      <p>URL: https://doi.org/10.1145/2845915. doi:1 0 . 1 1 4 5 / 2 8 4 5 9 1 5 .
[5] D. Abadi, A. Ailamaki, D. Andersen, P. Bailis, M. Balazinska, P. Bernstein, P. Boncz,
S. Chaudhuri, A. Cheung, A. Doan, et al., The seattle report on database research, SIGMOD
Rec. 48 (2020) 44–53. doi:1 0 . 1 1 4 5 / 3 3 8 5 6 5 8 . 3 3 8 5 6 6 8 .
[6] S. Sakr, Cloud-hosted databases: technologies, challenges and opportunities, Cluster</p>
      <p>Computing 17 (2014) 487–502. doi:1 0 . 1 0 0 7 / s 1 0 5 8 6 - 0 1 3 - 0 2 9 0 - 7 .
[7] M. Stonebraker, A. Pavlo, R. Taft, M. L. Brodie, Enterprise database applications and the
cloud: A dificult road ahead, in: 2014 IEEE International Conference on Cloud Engineering,
IEEE, 2014, pp. 1–6. doi:1 0 . 1 1 0 9 / I C 2 E . 2 0 1 4 . 9 7 .
[8] D. Seybold, Towards a framework for orchestrated distributed database evaluation in
the cloud, in: Proceedings of the 18th Doctoral Symposium of the 18th International
Middleware Conference, Middleware ’17, ACM, New York, NY, USA, 2017, pp. 13–14.
doi:1 0 . 1 1 4 5 / 3 1 5 2 6 8 8 . 3 1 5 2 6 9 3 .
[9] J. Domaschka, D. Seybold, Towards understanding the performance of distributed database
management systems in volatile environments, in: Symposium on Software
Performance, volume 39, Gesellschaft für Informatik, 2019, pp. 11–13. URL: https://pi.informatik.
uni-siegen.de/stt/39_4/01_Fachgruppenberichte/SSP2019/SSP2019_Domaschka.pdf.
[10] D. Seybold, M. Keppler, D. Gründler, J. Domaschka, Mowgli: Finding your way in the dbms
jungle, in: Proceedings of the 2019 ACM/SPEC International Conference on Performance
Engineering, ICPE ’19, ACM, New York, NY, USA, 2019, pp. 321–332. doi:1 0 . 1 1 4 5 / 3 2 9 7 6 6 3 .
3 3 1 0 3 0 3 .
[11] D. Seybold, J. Domaschka, Is distributed database evaluation cloud-ready?, in: European
Conference on Advances in Databases and Information Systems (ADBIS) - New Trends
in Databases and Information Systems (Short Papers), Springer International Publishing,
Cham, 2017, pp. 100–108. doi:1 0 . 1 0 0 7 / 9 7 8 - 3 - 3 1 9 - 6 7 1 6 2 - 8 _ 1 2 .
[12] D. Seybold, An automation-based approach for reproducible evaluations of distributed
DBMS on elastic infrastructures, Ph.D. thesis, 2021. URL: https://oparu.uni-ulm.de/xmlui/
handle/123456789/37430. doi:1 0 . 1 8 7 2 5 / O P A R U - 3 7 3 6 8 .
[13] D. Seybold, S. Volpert, S. Wesner, A. Bauer, N. Herbst, J. Domaschka, Kaa: Evaluating
elasticity of cloud-hosted dbms, in: 2019 IEEE International Conference on Cloud Computing
Technology and Science (CloudCom), 2019, pp. 54–61. doi:1 0 . 1 1 0 9 / C l o u d C o m . 2 0 1 9 . 0 0 0 2 0 .
[14] D. Seybold, S. Wesner, J. Domaschka, King louie: Reproducible availability benchmarking
of cloud-hosted dbms, in: 35th ACM/SIGAPP Symposium on Applied Computing (SAC
’20), March 30-April 3, 2020, Brno, Czech Republic, 2020, pp. 144–153. doi:1 0 . 1 1 4 5 / 3 3 4 1 1 0 5 .
3 3 7 3 9 6 8 .
[15] J. Domaschka, S. Volpert, D. Seybold, Hathi: An mcdm-based approach to capacity planning
for cloud-hosted dbms, in: 2020 IEEE/ACM 13th International Conference on Utility and
Cloud Computing (UCC), 2020, pp. 143–154. doi:1 0 . 1 1 0 9 / U C C 4 8 9 8 0 . 2 0 2 0 . 0 0 0 3 3 .</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A.</given-names>
            <surname>Davoudian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Chen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Liu</surname>
          </string-name>
          ,
          <article-title>A survey on nosql stores</article-title>
          ,
          <source>ACM Comput. Surv</source>
          .
          <volume>51</volume>
          (
          <year>2018</year>
          ).
          <source>doi:1 0 . 1 1</source>
          <volume>4 5 / 3 1 5 8 6 6 1 .</volume>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>S.</given-names>
            <surname>Mazumdar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Seybold</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kritikos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Verginadis</surname>
          </string-name>
          ,
          <article-title>A survey on data storage and placement methodologies for cloud-big data ecosystem</article-title>
          ,
          <source>Journal of Big Data</source>
          <volume>6</volume>
          (
          <year>2019</year>
          )
          <article-title>15</article-title>
          .
          <source>doi:1 0 . 1 1 8 6 / s 4 0</source>
          <volume>5 3 7 - 0 1 9 - 0 1 7 8 - 3</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>K.</given-names>
            <surname>Grolinger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W. A.</given-names>
            <surname>Higashino</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Tiwari</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. A.</given-names>
            <surname>Capretz</surname>
          </string-name>
          ,
          <article-title>Data management in cloud environments: Nosql and newsql data stores</article-title>
          ,
          <source>Journal of Cloud Computing: Advances, Systems and Applications</source>
          <volume>2</volume>
          (
          <year>2013</year>
          )
          <article-title>22</article-title>
          .
          <source>doi:1 0 . 1 1</source>
          <volume>8 6 / 2 1 9 2 - 1 1 3 X - 2 - 2</volume>
          <fpage>2</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>D.</given-names>
            <surname>Abadi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Agrawal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ailamaki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Balazinska</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. A.</given-names>
            <surname>Bernstein</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Carey</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Chaudhuri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Dean</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Doan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Franklin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Gehrke</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. M.</given-names>
            <surname>Haas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. Y.</given-names>
            <surname>Halevy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. M.</given-names>
            <surname>Hellerstein</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y. E.</given-names>
            <surname>Ioannidis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H. V.</given-names>
            <surname>Jagadish</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Kossmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Madden</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Mehrotra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Milo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. F.</given-names>
            <surname>Naughton</surname>
          </string-name>
          ,
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>