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_dbt2_5_tb

101 views

Published on

Report of running DBT2 benchmark using NDB Cluster on Intel Server with 6 TByte of Persistent Memory in Memory Mode

Published in: Software
  • Be the first to comment

Ndb cluster 80_dbt2_5_tb

  1. 1. Copyright © 2020 Oracle and/or its affiliates. MySQL NDB Cluster 8.0, DBT2 Benchmark with 5TB Data MySQL Cluster Development Mikael Ronström
  2. 2. • 1 Data Node • Intel Xeon Platinum 8260L @2.40 GHz • 6 TB Intel Optane DC Persistent Memory • 768 GB RAM • Persistent Memory used in Memory mode • DBT2 based on TPC-C specs with zero delay between transactions DBT2 Benchmark Definition
  3. 3. Persistent Memory Model in Benchmark CPU CPU Caches DRAM Persistent Memory • Intel Xeon Platinum 8260L @2.40 GHz 768 GB DRAM 6 TB Intel Optane DC Persistent Memory
  4. 4. • Memory Mode => Memory cleared at restart, used as normal memory • App Direct Mode => Memory remains after restart • In experiment here we used Memory Mode Persistent Memory Models
  5. 5. DBT2 Benchmark Layout DBT2 Driver DBT2 Client 1 MySQL Server 1 NDB Data Node Intel Xeon Platinum 8260L @2.40 GHz 2 sockets with total of 48 cores
  6. 6. • Parallel LOAD DATA INFILE in 32 threads • > 2 warehouses loaded per second • 1 warehouse = 500.000 rows • => More than 1 M Inserts per second • 45.000 warehouses loaded in about 8 hours • Number of warehouses limited by 5.9 TB SSD for REDO log and checkpoint data, could load roughly 53.000 warehouses with a larger SSD, will be verified later DBT2 Load Phase
  7. 7. • DBT2 ran with 2 up to 512 threads. Default mode of DBT2 is to use the warehouse id = thread id • Default mode means all data accesses finds data in DRAM cache (768 G in size) • DBT2 altered mode means used warehouse is random and thus benchmark will cause misses in DRAM cache that requires reading and writing data in Persistent Memory layer DBT2 Benchmark run
  8. 8. DBT2 Benchmark Results TPM 0 100000 200000 300000 400000 2 8 16 32 64 128 192 256 384 512 Default Mode Altered Mode
  9. 9. • Optane memory increases transaction latency by 10-12% when accessing the full range of 5 TB data • Benchmark limited by MySQL Server, handles 370k TPM on a single server with 5 TB user data • NDB Cluster verified to handle properly DB sizes up to 5 TB on one single 2 CPU Socket node • With Optane DC Persistent Memory the recommendation is to use hyperthreading also on LDM threads DBT2 5 TB Conclusions
  10. 10. • MySQL Server used 1 socket + 3 cores • Benchmark used 2 cores • NDB Data Node used 19 cores (24 LDM threads on 12 cores) • Base latency was around 7 ms for NewOrder transactions (fairly complex transactions, lots of SQL statements) Benchmark Configuration
  11. 11. Thank you!

×