m4max-server Apple M4 Max testing with a Apple MacBook Pro and Apple M4 Max on macOS 15.1 via the Phoronix Test Suite. m4max-server: Processor: Apple M4 Max (16 Cores), Motherboard: Apple MacBook Pro, Memory: 128GB, Disk: 1859GB, Graphics: Apple M4 Max, Monitor: Color LCD OS: macOS 15.1, Kernel: 24.1.0 (arm64), Compiler: GCC 16.0.0 + Clang 16.0.0, File-System: APFS, Screen Resolution: 3456x2234 LevelDB 1.23 Benchmark: Hot Read Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Fill Sync Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Overwrite Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Random Fill Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Random Read Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Seek Random Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Random Delete Microseconds Per Op < Lower Is Better LevelDB 1.23 Benchmark: Sequential Fill Microseconds Per Op < Lower Is Better SQLite 3.30.1 Threads / Copies: 1 Seconds < Lower Is Better m4max-server . 7.320 |========================================================= BlogBench 1.1 Test: Read Final Score > Higher Is Better m4max-server . 55188 |========================================================= BlogBench 1.1 Test: Write Final Score > Higher Is Better m4max-server . 292 |=========================================================== simdjson 3.10 Throughput Test: Kostya GB/s > Higher Is Better m4max-server . 4.71 |========================================================== simdjson 3.10 Throughput Test: TopTweet GB/s > Higher Is Better m4max-server . 7.03 |========================================================== simdjson 3.10 Throughput Test: LargeRandom GB/s > Higher Is Better m4max-server . 1.78 |========================================================== simdjson 3.10 Throughput Test: PartialTweets GB/s > Higher Is Better m4max-server . 6.88 |========================================================== simdjson 3.10 Throughput Test: DistinctUserID GB/s > Higher Is Better m4max-server . 7.07 |========================================================== Node.js Express HTTP Load Test Requests Per Second > Higher Is Better Perl Benchmarks Test: Pod2html Seconds < Lower Is Better Perl Benchmarks Test: Interpreter Seconds < Lower Is Better OpenSSL 3.3 Algorithm: SHA256 OpenSSL 3.3 Algorithm: SHA512 OpenSSL 3.3 Algorithm: RSA4096 OpenSSL 3.3 Algorithm: ChaCha20 OpenSSL 3.3 Algorithm: AES-128-GCM OpenSSL 3.3 Algorithm: AES-256-GCM OpenSSL 3.3 Algorithm: ChaCha20-Poly1305 Node.js V8 Web Tooling Benchmark runs/s > Higher Is Better m4max-server . 39.07 |========================================================= MariaDB mariadb-slap 11.5 Clients: 1 Queries Per Second > Higher Is Better MariaDB mariadb-slap 11.5 Clients: 32 Queries Per Second > Higher Is Better MariaDB mariadb-slap 11.5 Clients: 64 Queries Per Second > Higher Is Better MariaDB mariadb-slap 11.5 Clients: 128 Queries Per Second > Higher Is Better MariaDB mariadb-slap 11.5 Clients: 256 Queries Per Second > Higher Is Better MariaDB mariadb-slap 11.5 Clients: 512 Queries Per Second > Higher Is Better MariaDB mariadb-slap 11.5 Clients: 1024 Queries Per Second > Higher Is Better MariaDB mariadb-slap 11.5 Clients: 2048 Queries Per Second > Higher Is Better MariaDB mariadb-slap 11.5 Clients: 4096 Queries Per Second > Higher Is Better MariaDB mariadb-slap 11.5 Clients: 8192 Queries Per Second > Higher Is Better DuckDB 1.0 Benchmark: IMDB Seconds < Lower Is Better m4max-server . 45.12 |========================================================= DuckDB 1.0 Benchmark: Clickbench Seconds < Lower Is Better m4max-server . 13.41 |========================================================= DuckDB 1.0 Benchmark: TPC-H Parquet Seconds < Lower Is Better m4max-server . 75.96 |========================================================= PostgreSQL 17 Scaling Factor: 1 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 1 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 1 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 50 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 100 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 100 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 250 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 50 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 500 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 800 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 1000 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 100 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 1000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 250 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 500 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 5000 - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 800 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 10000 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 1000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling Factor: 25000 - Clients: 5000 - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling: Buffer Test - Test: Normal Load - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling: Buffer Test - Test: Normal Load - Mode: Read Write TPS > Higher Is Better PostgreSQL 17 Scaling: Buffer Test - Test: Heavy Contention - Mode: Read Only TPS > Higher Is Better PostgreSQL 17 Scaling: Buffer Test - Test: Heavy Contention - Mode: Read Write TPS > Higher Is Better SQLite Speedtest 3.30 Timed Time - Size 1,000 Seconds < Lower Is Better m4max-server . 59.52 |========================================================= nginx 1.23.2 Connections: 1 Requests Per Second > Higher Is Better nginx 1.23.2 Connections: 20 Requests Per Second > Higher Is Better nginx 1.23.2 Connections: 100 Requests Per Second > Higher Is Better nginx 1.23.2 Connections: 200 Requests Per Second > Higher Is Better nginx 1.23.2 Connections: 500 Requests Per Second > Higher Is Better nginx 1.23.2 Connections: 1000 Requests Per Second > Higher Is Better nginx 1.23.2 Connections: 4000 Requests Per Second > Higher Is Better Apache HTTP Server 2.4.56 Concurrent Requests: 4 Requests Per Second > Higher Is Better Apache HTTP Server 2.4.56 Concurrent Requests: 20 Requests Per Second > Higher Is Better m4max-server . 38918.90 |====================================================== Apache HTTP Server 2.4.56 Concurrent Requests: 100 Requests Per Second > Higher Is Better m4max-server . 41071.13 |====================================================== Apache HTTP Server 2.4.56 Concurrent Requests: 200 Requests Per Second > Higher Is Better m4max-server . 41136.77 |====================================================== Apache HTTP Server 2.4.56 Concurrent Requests: 500 Requests Per Second > Higher Is Better m4max-server . 41684.79 |====================================================== Apache HTTP Server 2.4.56 Concurrent Requests: 1000 Requests Per Second > Higher Is Better m4max-server . 41758.75 |====================================================== Apache Siege 2.4.62 Concurrent Users: 200 Transactions Per Second > Higher Is Better Apache Siege 2.4.62 Concurrent Users: 250 Transactions Per Second > Higher Is Better PHPBench 0.8.1 PHP Benchmark Suite Score > Higher Is Better m4max-server . 1134380 |======================================================= PHP Micro Benchmarks Test: Zend bench Seconds < Lower Is Better m4max-server . 0.290 |========================================================= PHP Micro Benchmarks Test: Zend micro_bench Seconds < Lower Is Better m4max-server . 1.334 |=========================================================