Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Ndb cluster 80_oci_dbt2

DBT2 benchmarks of MySQL NDB Cluster 8.0 in the Oracle Cloud

  • Be the first to comment

Ndb cluster 80_oci_dbt2

  1. 1. Copyright © 2020 Oracle and/or its affiliates. MySQL NDB Cluster 8.0, DBT2 Benchmark in Oracle Cloud MySQL Cluster Development Mikael Ronström
  2. 2. • 6 Data Node, DenseIO BareMetal, 52 CPU cores • 15 MySQL Server Nodes, Bare Metal, 36 CPU cores • 1 Bare Metal 36 CPU core running DBT2 Driver and Client • DBT2 based on TPC-C specs with zero delay between transactions DBT2 Benchmark Definition
  3. 3. • Parallel LOAD DATA INFILE • > 2 warehouses loaded per second • 1 warehouse = 500.000 rows • => More than 1 M Inserts per second • Around 3M inserts per second for 3 NGs and 2 Replicas DBT2 Load Phase
  4. 4. DBT2 Benchmark Layout DBT2 Driver DBT2 Client MySQL Server NDB Data Nodes DBT2 Driver and Client runs on one benchmark Server in AD 3 where also ndb_mgmd runs
  5. 5. 2 Replicas, 1 Node Group mysqld mysqld mysqld mysqld mysqld AD 2 ndbmtd ndbmtd mysqld mysqld mysqld mysqld mysqld AD 3 Node Group
  6. 6. DBT2 Results, 2 Replicas, 1 Node Group TPM 0 350000 700000 1050000 1400000 Connections 10 40 160 320 640 1280 1920 2560 DBT2 2 Replicas, 1 Node Group
  7. 7. 2 Replicas, 3 Node Groups ndbmtd ndbmtd mysqld mysqld mysqld mysqld mysqld AD 1 ndbmtd ndbmtd mysqld mysqld mysqld mysqld mysqld AD 2 ndbmtd ndbmtd mysqld mysqld mysqld mysqld mysqld AD 3 Node Group Node Group NG
  8. 8. DBT2 Results, 2 Replicas, 3 Node Groups TPM 0 1000000 2000000 3000000 4000000 5000000 Connections 15 30 60 120 240 480 960 1920 3840 5760 7200 9000 10800 12000 144000 DBT2 2 Replicas, 3 Node Groups
  9. 9. 3 Replicas, 2 Node Groups ndbmtd ndbmtd mysqld mysqld mysqld mysqld mysqld AD 1 ndbmtd ndbmtd mysqld mysqld mysqld mysqld mysqld AD 2 ndbmtd ndbmtd mysqld mysqld mysqld mysqld mysqld AD 3 Node Group Node Group
  10. 10. DBT2 Results, 3 Replicas, 2 Node Groups TPM 0 750000 1500000 2250000 3000000 Connections 1 2 4 8 16 32 64 120 240 480 960 1800 2700 3600 4800 6000 7200 8400 9000 9600 DBT2 3 Replica, 2 Node Groups
  11. 11. • MySQL Server and data in different ADs cause latency • NDB Data Nodes is limiting in this benchmark • 4M TPM reached using 770 MySQL Server CPUs and 340 CPUs for NDB Data Nodes • 4M TPM corresponds to roughly 3.6M SQL queries per second • 22 Bare Metal Servers used (1 ran benchmark) DBT2 Oracle Cloud Conclusions

×