pts-database

Apple M2 Pro testing with a Apple Mac mini and Apple M2 Pro on macOS 13.5 via the Phoronix Test Suite.

Compare your own system(s) to this result file with the Phoronix Test Suite by running the command: phoronix-test-suite benchmark 2312090-NE-PTSDATABA57
Jump To Table - Results

Statistics

Remove Outliers Before Calculating Averages

Graph Settings

Prefer Vertical Bar Graphs

Multi-Way Comparison

Condense Multi-Option Tests Into Single Result Graphs

Table

Show Detailed System Result Table

Run Management

Result
Identifier
View Logs
Performance Per
Dollar
Date
Run
  Test
  Duration
pts-database
December 09 2023
  1 Hour
Only show results matching title/arguments (delimit multiple options with a comma):
Do not show results matching title/arguments (delimit multiple options with a comma):

pts-database Apple M2 Pro testing with a Apple Mac mini and Apple M2 Pro on macOS 13.5 via the Phoronix Test Suite. pts-database: Processor: Apple M2 Pro (10 Cores), Motherboard: Apple Mac mini, Memory: 16GB, Disk: 461GB, Graphics: Apple M2 Pro, Monitor: Apple M2 Pro OS: macOS 13.5, Kernel: 22.6.0 (arm64), Compiler: GCC 14.0.3 + Clang 17.0.6 + LLVM 17.0.6 + Xcode 14.3.1, File-System: APFS, Screen Resolution: x DuckDB 0.9.1 Benchmark: IMDB Seconds < Lower Is Better pts-database . 127.56 |======================================================== DuckDB 0.9.1 Benchmark: TPC-H Parquet Seconds < Lower Is Better pts-database . 93.57 |========================================================= SQLite Speedtest 3.30 Timed Time - Size 1,000 Seconds < Lower Is Better pts-database . 53.01 |========================================================= PostgreSQL 16 Scaling Factor: 1 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 10000 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 1000 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 100 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 16 Scaling Factor: 25000 - Clients: 250 - Mode: Read Write TPS > Higher Is Better SQLite 3.30.1 Threads / Copies: 1 Seconds < Lower Is Better MariaDB 11.0.1 Clients: 1 Queries Per Second > Higher Is Better LevelDB 1.23 Benchmark: Hot Read Microseconds Per Op < Lower Is Better MariaDB 11.0.1 Clients: 8192 Queries Per Second > Higher Is Better MariaDB 11.0.1 Clients: 4096 Queries Per Second > Higher Is Better MariaDB 11.0.1 Clients: 2048 Queries Per Second > Higher Is Better MariaDB 11.0.1 Clients: 1024 Queries Per Second > Higher Is Better MariaDB 11.0.1 Clients: 512 Queries Per Second > Higher Is Better MariaDB 11.0.1 Clients: 256 Queries Per Second > Higher Is Better MariaDB 11.0.1 Clients: 128 Queries Per Second > Higher Is Better MariaDB 11.0.1 Clients: 64 Queries Per Second > Higher Is Better LevelDB 1.23 Benchmark: Sequential Fill Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Random Delete Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Seek Random Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Random Read Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Random Fill Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Overwrite Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Fill Sync Microseconds Per Op < Lower Is Better