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

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

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.

Algorithm: SHA512

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: ChaCha20

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

Algorithm: AES-128-GCM

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-Poly1305

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

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.

simdjson

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

Clients: 32

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: 128

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: 512

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: 2048

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: 8192

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

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.

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.

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

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: 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: 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: 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: 4000

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

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.

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.

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.