Overview

Pinned:

• Benchmarks

Posts for 2020:

• Explaining explain to understand index usage in MySQL

Benchmark reports for 2022:

• Insert Benchmark to test wal_compression in Postgres 15
  • Intel NUC, IO-bound
  • Intel NUC, not IO-bound
• Insert Benchmark for Postgres 12.11, 13.7, 14.3 and 15b1
  • Intel NUC, IO-bound
  • Intel NUC, IO-bound, uses prepared statements
  • Intel NUC, IO-bound, uses prepared statements, 15b1 with patch 1
  • Intel NUC, not IO-bound
  • Intel NUC, not IO-bound, uses prepared statements
  • Intel NUC, not IO-bound, uses prepared statements, 15b1 with patch 1
• Insert Benchmark for Postgres 14.0, 14.1, 14.2, 14.3
  • Intel NUC, IO-bound
  • Intel NUC, not IO-bound

Benchmark reports for 2021:

• November
  • Insert benchmark, Intel NUC, 1 user, 20M rows (in memory)
    • InnoDB in MySQL 5.6, 5.7 and 8.0
    • Postgres 12.4, 13.4 and 14.0
    • MyRocks 5.6.35 and 8.0.20
  • Insert benchmark, Intel NUC, 1 user, 500M rows (IO-bound)
    • InnoDB in MySQL 5.6, 5.7 and 8.0
    • Postgres 12.4, 13.4 and 14.0
    • MyRocks 5.6.35 and 8.0.20
• January, Intel NUC
  • Insert benchmark, 20M rows, 1 user, NUC server
  • Insert benchmark, 100M rows, 1 user, NUC server
  • Insert benchmark, 500M rows, 1 user, NUC server

Benchmark reports for 2020:

• Insert benchmark tests with a table per user
  • CPU-bound, 15m rows, 1 user
  • CPU-bound, 40m rows, 8 user
  • IO-bound 800m rows, 8 users
  • IO-bound 2000m rows, 8 users
• Insert benchmark tests with 1 table shared by all users
  • CPU-bound, 40m rows, 8 user
  • IO-bound 800m rows, 8 users
  • IO-bound 2000m rows, 8 users
• Linkbench
  • CPU-bound, maxid1=10m, 8 users
  • IO-bound, maxid1=200m, 8 users
  • IO-bound, maxid1=500m, 8 users
• Insert benchmark on NUC to determine the best configuration
  • CPU-bound, 20m rows for InnoDB, MyRocks and Postgres
  • Less IO-bound, 100m rows for InnoDB, MyRocks and Postgres
  • More IO-bound, 500m rows for InnoDB, MyRocks and Postgres