m4max-server

Apple M4 Max testing with a Apple MacBook Pro and Apple M4 Max on macOS 15.1 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 2411187-NE-M4MAXSERV89
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
m4max-server
November 18
  2 Hours, 27 Minutes
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):

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

Environment Notes: XPC_FLAGS=0x0

BlogBench

BlogBench is designed to replicate the load of a real-world busy file server by stressing the file-system with multiple threads of random reads, writes, and rewrites. The behavior is mimicked of that of a blog by creating blogs with content and pictures, modifying blog posts, adding comments to these blogs, and then reading the content of the blogs. All of these blogs generated are created locally with fake content and pictures. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgFinal Score, More Is BetterBlogBench 1.1Test: Readm4max-server12K24K36K48K60KSE +/- 2241.13, N = 6551881. (CC) gcc options: -O2

SQLite Speedtest

This is a benchmark of SQLite's speedtest1 benchmark program with an increased problem size of 1,000. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgSeconds, Fewer Is BetterSQLite Speedtest 3.30Timed Time - Size 1,000m4max-server1326395265SE +/- 19.71, N = 1559.521. (CC) gcc options: -O2 -lz

DuckDB

OpenBenchmarking.orgSeconds, Fewer Is BetterDuckDB 1.0Benchmark: IMDBm4max-server1020304050SE +/- 0.11, N = 345.121. (CXX) g++ options: -O3 -arch -isysroot

OpenBenchmarking.orgSeconds, Fewer Is BetterDuckDB 1.0Benchmark: TPC-H Parquetm4max-server20406080100SE +/- 0.13, N = 375.961. (CXX) g++ options: -O3 -arch -isysroot

Apache HTTP Server

This is a test of the Apache HTTPD web server. This Apache HTTPD web server benchmark test profile makes use of the wrk program for facilitating the HTTP requests over a fixed period time with a configurable number of concurrent clients. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgRequests Per Second, More Is BetterApache HTTP Server 2.4.56Concurrent Requests: 20m4max-server8K16K24K32K40KSE +/- 145.06, N = 338918.901. (CC) gcc options: -lluajit-5.1 -lm -lssl -lcrypto -lpthread -std=c99 -O2

OpenBenchmarking.orgRequests Per Second, More Is BetterApache HTTP Server 2.4.56Concurrent Requests: 500m4max-server9K18K27K36K45KSE +/- 409.69, N = 341684.791. (CC) gcc options: -lluajit-5.1 -lm -lssl -lcrypto -lpthread -std=c99 -O2

OpenBenchmarking.orgRequests Per Second, More Is BetterApache HTTP Server 2.4.56Concurrent Requests: 100m4max-server9K18K27K36K45KSE +/- 200.48, N = 341071.131. (CC) gcc options: -lluajit-5.1 -lm -lssl -lcrypto -lpthread -std=c99 -O2

OpenBenchmarking.orgRequests Per Second, More Is BetterApache HTTP Server 2.4.56Concurrent Requests: 1000m4max-server9K18K27K36K45KSE +/- 123.45, N = 341758.751. (CC) gcc options: -lluajit-5.1 -lm -lssl -lcrypto -lpthread -std=c99 -O2

OpenBenchmarking.orgRequests Per Second, More Is BetterApache HTTP Server 2.4.56Concurrent Requests: 200m4max-server9K18K27K36K45KSE +/- 73.52, N = 341136.771. (CC) gcc options: -lluajit-5.1 -lm -lssl -lcrypto -lpthread -std=c99 -O2

simdjson

OpenBenchmarking.orgGB/s, More Is Bettersimdjson 3.10Throughput Test: Kostyam4max-server1.05982.11963.17944.23925.299SE +/- 0.00, N = 34.711. (CXX) g++ options: -O3 -arch -isysroot

OpenBenchmarking.orgGB/s, More Is Bettersimdjson 3.10Throughput Test: LargeRandomm4max-server0.40050.8011.20151.6022.0025SE +/- 0.01, N = 31.781. (CXX) g++ options: -O3 -arch -isysroot

OpenBenchmarking.orgGB/s, More Is Bettersimdjson 3.10Throughput Test: TopTweetm4max-server246810SE +/- 0.00, N = 37.031. (CXX) g++ options: -O3 -arch -isysroot

OpenBenchmarking.orgGB/s, More Is Bettersimdjson 3.10Throughput Test: DistinctUserIDm4max-server246810SE +/- 0.00, N = 37.071. (CXX) g++ options: -O3 -arch -isysroot

OpenBenchmarking.orgGB/s, More Is Bettersimdjson 3.10Throughput Test: PartialTweetsm4max-server246810SE +/- 0.00, N = 36.881. (CXX) g++ options: -O3 -arch -isysroot

Node.js V8 Web Tooling Benchmark

Running the V8 project's Web-Tooling-Benchmark under Node.js. The Web-Tooling-Benchmark stresses JavaScript-related workloads common to web developers like Babel and TypeScript and Babylon. This test profile can test the system's JavaScript performance with Node.js. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgruns/s, More Is BetterNode.js V8 Web Tooling Benchmarkm4max-server918273645SE +/- 0.28, N = 339.07

SQLite

This is a simple benchmark of SQLite. At present this test profile just measures the time to perform a pre-defined number of insertions on an indexed database. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgSeconds, Fewer Is BetterSQLite 3.30.1Threads / Copies: 1m4max-server246810SE +/- 0.696, N = 157.3201. (CC) gcc options: -O2 -lreadline -ltermcap -lz

DuckDB

OpenBenchmarking.orgSeconds, Fewer Is BetterDuckDB 1.0Benchmark: Clickbenchm4max-server3691215SE +/- 0.03, N = 313.411. (CXX) g++ options: -O3 -arch -isysroot

PostgreSQL

Scaling Factor: 1 - Clients: 100 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

PHPBench

PHPBench is a benchmark suite for PHP. It performs a large number of simple tests in order to bench various aspects of the PHP interpreter. PHPBench can be used to compare hardware, operating systems, PHP versions, PHP accelerators and caches, compiler options, etc. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgScore, More Is BetterPHPBench 0.8.1PHP Benchmark Suitem4max-server200K400K600K800K1000KSE +/- 3272.80, N = 31134380

Node.js Express HTTP Load Test

A Node.js Express server with a Node-based loadtest client for facilitating HTTP benchmarking. Learn more via the OpenBenchmarking.org test page.

m4max-server: The test run did not produce a result.

PostgreSQL

Scaling Factor: 1 - Clients: 1 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 500 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 250 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 1 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 1 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 500 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling: Buffer Test - Test: Heavy Contention - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling: Buffer Test - Test: Normal Load - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 5000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 1000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 500 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 250 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 100 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 500 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 250 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 50 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 100 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 800 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 500 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 250 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 100 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 1 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 800 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 50 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 1 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling: Buffer Test - Test: Heavy Contention - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling: Buffer Test - Test: Normal Load - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 1000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 5000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 800 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 5000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 800 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 5000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 100 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 5000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 1000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 800 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 50 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 100 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 800 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 500 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 100 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 800 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 500 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 1000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 100 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 5000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 1000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 50 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 1 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 50 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 800 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 500 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 250 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 5000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 1000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 1 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 50 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 1 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 800 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 50 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 250 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 5000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 1000 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 1 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 50 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 5000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 500 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 250 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 1000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 1 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 800 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 500 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 250 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 25000 - Clients: 1000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 250 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 1000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 50 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 10000 - Clients: 250 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1000 - Clients: 5000 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 100 - Clients: 100 - Mode: Read Only

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 100 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

Scaling Factor: 1 - Clients: 50 - Mode: Read Write

m4max-server: The test run did not produce a result. E: pgbench: line 21: pg_/bin/pgbench: No such file or directory

PHP Micro Benchmarks

Various small PHP micro-benchmarks. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgSeconds, Fewer Is BetterPHP Micro BenchmarksTest: Zend micro_benchm4max-server0.30020.60040.90061.20081.501SE +/- 0.006, N = 31.334

OpenBenchmarking.orgSeconds, Fewer Is BetterPHP Micro BenchmarksTest: Zend benchm4max-server0.06530.13060.19590.26120.3265SE +/- 0.003, N = 30.290

Perl Benchmarks

Perl benchmark suite that can be used to compare the relative speed of different versions of perl. Learn more via the OpenBenchmarking.org test page.

Test: Pod2html

m4max-server: The test run did not produce a result. E: cat: 'perlbench-results/*/perls/*/tests/*': No such file or directory

nginx

This is a benchmark of the lightweight Nginx HTTP(S) web-server. This Nginx web server benchmark test profile makes use of the wrk program for facilitating the HTTP requests over a fixed period time with a configurable number of concurrent clients/connections. HTTPS with a self-signed OpenSSL certificate is used by this test for local benchmarking. Learn more via the OpenBenchmarking.org test page.

Connections: 1

m4max-server: The test quit with a non-zero exit status.

OpenSSL

OpenSSL is an open-source toolkit that implements SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols. This test profile makes use of the built-in "openssl speed" benchmarking capabilities. Learn more via the OpenBenchmarking.org test page.

Algorithm: SHA256

m4max-server: The test quit with a non-zero exit status.

Apache HTTP Server

This is a test of the Apache HTTPD web server. This Apache HTTPD web server benchmark test profile makes use of the wrk program for facilitating the HTTP requests over a fixed period time with a configurable number of concurrent clients. Learn more via the OpenBenchmarking.org test page.

Concurrent Requests: 4

m4max-server: The test quit with a non-zero exit status.

Apache Siege

Concurrent Users: 200

m4max-server: The test run did not produce a result. E: apache-siege: line 5: ./siege: No such file or directory

MariaDB mariadb-slap

This is a MariaDB MySQL database server benchmark making use of mysqlslap (mariadb-slap). Learn more via the OpenBenchmarking.org test page.

Clients: 1

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

LevelDB

LevelDB is a key-value storage library developed by Google that supports making use of Snappy for data compression and has other modern features. Learn more via the OpenBenchmarking.org test page.

Benchmark: Hot Read

m4max-server: The test run did not produce a result. E: leveldb: line 3: ./db_bench: No such file or directory

Perl Benchmarks

Perl benchmark suite that can be used to compare the relative speed of different versions of perl. Learn more via the OpenBenchmarking.org test page.

Test: Interpreter

m4max-server: The test run did not produce a result. E: cat: 'perlbench-results/*/perls/*/tests/*': No such file or directory

Apache Siege

Concurrent Users: 250

m4max-server: The test run did not produce a result. E: apache-siege: line 5: ./siege: No such file or directory

nginx

This is a benchmark of the lightweight Nginx HTTP(S) web-server. This Nginx web server benchmark test profile makes use of the wrk program for facilitating the HTTP requests over a fixed period time with a configurable number of concurrent clients/connections. HTTPS with a self-signed OpenSSL certificate is used by this test for local benchmarking. Learn more via the OpenBenchmarking.org test page.

Connections: 4000

m4max-server: The test quit with a non-zero exit status. E: unable to connect to 127.0.0.1:8089 Connection refused

Connections: 1000

m4max-server: The test quit with a non-zero exit status. E: unable to connect to 127.0.0.1:8089 Connection refused

Connections: 500

m4max-server: The test quit with a non-zero exit status. E: unable to connect to 127.0.0.1:8089 Connection refused

Connections: 200

m4max-server: The test quit with a non-zero exit status. E: unable to connect to 127.0.0.1:8089 Connection refused

Connections: 100

m4max-server: The test quit with a non-zero exit status. E: unable to connect to 127.0.0.1:8089 Connection refused

Connections: 20

m4max-server: The test quit with a non-zero exit status. E: unable to connect to 127.0.0.1:8089 Connection refused

OpenSSL

OpenSSL is an open-source toolkit that implements SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols. This test profile makes use of the built-in "openssl speed" benchmarking capabilities. Learn more via the OpenBenchmarking.org test page.

Algorithm: AES-128-GCM

m4max-server: The test quit with a non-zero exit status.

LevelDB

LevelDB is a key-value storage library developed by Google that supports making use of Snappy for data compression and has other modern features. Learn more via the OpenBenchmarking.org test page.

Benchmark: Fill Sync

m4max-server: The test run did not produce a result. E: leveldb: line 3: ./db_bench: No such file or directory

MariaDB mariadb-slap

This is a MariaDB MySQL database server benchmark making use of mysqlslap (mariadb-slap). Learn more via the OpenBenchmarking.org test page.

Clients: 8192

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

Clients: 4096

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

Clients: 2048

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

Clients: 1024

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

Clients: 512

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

Clients: 256

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

Clients: 128

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

Clients: 64

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

Clients: 32

m4max-server: The test quit with a non-zero exit status. E: mysqlslap: line 3: ./bin/mysqlslap: No such file or directory

OpenSSL

OpenSSL is an open-source toolkit that implements SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols. This test profile makes use of the built-in "openssl speed" benchmarking capabilities. Learn more via the OpenBenchmarking.org test page.

Algorithm: ChaCha20-Poly1305

m4max-server: The test quit with a non-zero exit status.

Algorithm: AES-256-GCM

m4max-server: The test quit with a non-zero exit status.

Algorithm: ChaCha20

m4max-server: The test quit with a non-zero exit status.

Algorithm: RSA4096

m4max-server: The test quit with a non-zero exit status.

Algorithm: SHA512

m4max-server: The test quit with a non-zero exit status.

LevelDB

LevelDB is a key-value storage library developed by Google that supports making use of Snappy for data compression and has other modern features. Learn more via the OpenBenchmarking.org test page.

Benchmark: Sequential Fill

m4max-server: The test run did not produce a result. E: leveldb: line 3: ./db_bench: No such file or directory

Benchmark: Random Delete

m4max-server: The test run did not produce a result. E: leveldb: line 3: ./db_bench: No such file or directory

Benchmark: Seek Random

m4max-server: The test run did not produce a result. E: leveldb: line 3: ./db_bench: No such file or directory

Benchmark: Random Read

m4max-server: The test run did not produce a result. E: leveldb: line 3: ./db_bench: No such file or directory

Benchmark: Random Fill

m4max-server: The test run did not produce a result. E: leveldb: line 3: ./db_bench: No such file or directory

Benchmark: Overwrite

m4max-server: The test run did not produce a result. E: leveldb: line 3: ./db_bench: No such file or directory

BlogBench

BlogBench is designed to replicate the load of a real-world busy file server by stressing the file-system with multiple threads of random reads, writes, and rewrites. The behavior is mimicked of that of a blog by creating blogs with content and pictures, modifying blog posts, adding comments to these blogs, and then reading the content of the blogs. All of these blogs generated are created locally with fake content and pictures. Learn more via the OpenBenchmarking.org test page.

OpenBenchmarking.orgFinal Score, More Is BetterBlogBench 1.1Test: Writem4max-server60120180240300SE +/- 18.88, N = 32921. (CC) gcc options: -O2

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

Environment Notes: XPC_FLAGS=0x0

Testing initiated at 18 November 2024 13:13 by user civil.