Skip to main content

PassMark

This benchmark measures CPUCPU: Central Processing UnitThe general-purpose processor of a computer, which runs the operating system and programs. A CPU has one or more physical cores, and with SMT each core runs two or more hardware threads.WikipediaGlossary and memory performance with PassMark's pt_linuxpt_linux: PerformanceTest for LinuxThe command-line edition of PassMark PerformanceTest for Linux on x86-64 and Arm64 processors. It runs the CPU and memory tests of PerformanceTest in a terminal interface, can run them unattended, and saves the results to a YAML file.PerformanceTest LinuxGlossary (PerformanceTest for Linux). It runs PassMark's CPU and memory test suites unattended, with PassMark's default test duration and iteration count, and passes PassMark's own results file through unchanged.

It reports the CPU MarkCPU MarkThe overall CPU score of PassMark PerformanceTest. It combines the results of the CPU tests, such as integer and floating-point math, prime numbers, sorting, encryption, compression, physics, and a single-threaded test, into one unitless number, where higher is better. PassMark Software publishes CPU Mark results submitted by users for thousands of processors.PassMark CPU BenchmarksGlossary and Memory MarkMemory MarkThe overall memory score of PassMark PerformanceTest. It combines the results of the memory tests, such as database operations, cached and uncached reads, writes, and latency, into one unitless number, where higher is better.PassMark Memory BenchmarksGlossary composite scores, together with the individual CPU and memory test results behind them, as a YAMLYAML: YAML Ain't Markup LanguageA human-readable text format for structured data, built from indented key-value mappings and lists. It is a superset of JSON, and is widely used for configuration files and for exchanging data between programs.YAML specificationGlossary document. Spare Cores Navigator publishes both marks and 14 of the individual test results; its Benchmark Workloads page describes each test and shows its score distribution.

Purpose​

This benchmark compares server types on the following PassMark tests, which the Navigator publishes:

  • CPU tests: integer and floating-point math, prime numbers, string sorting, encryption, compression, physics, extended instructions, and a single-threaded test.
  • Memory tests: database operations, cached and uncached reads, writes, and latency.

The Navigator already publishes other CPU and memory benchmarks. It adds PassMark because a run is short (2 to 3 minutes), the self-hosting community uses PassMark widely, and some of its tests, such as Database Operations, cover workloads that the other benchmarks do not.

It runs PassMark's tests without changing them, so PassMark, not Spare Cores, computes the composite scores.

Limitations​

These results compare servers on PassMark's synthetic CPU and memory tests, not on application throughput, and they exclude disk, network, and GPUGPU: Graphics Processing UnitA processor with thousands of simple cores that run the same operation on many data elements in parallel. It was built to render graphics, and is now also used for general-purpose parallel work such as machine learning training and inference, scientific simulation, and video encoding. Cloud providers rent GPUs attached to virtual machines, with their own dedicated GPU memory.WikipediaGlossary performance. The main limitations are the following:

  • Scaling: Many PassMark tests, including Database Operations, do not scale well above 32 vCPUsvCPU: virtual CPUA CPU of a virtual machine, the unit in which cloud vendors sell compute. It is usually one hardware thread of a physical core with SMT, so two vCPUs may share one physical core.WikipediaGlossary. Memory MarkMemory MarkThe overall memory score of PassMark PerformanceTest. It combines the results of the memory tests, such as database operations, cached and uncached reads, writes, and latency, into one unitless number, where higher is better.PassMark Memory BenchmarksGlossary does not scale well above 16 vCPUs: its scores plateau and may even degrade as the vCPU count increases. Production runs this benchmark only on servers with at most 32 vCPUs; the image does not enforce this limit and runs on any server.
  • PassMark Version: The image downloads the latest PassMark release when it is built, without a version pin, so a rebuild can change the PassMark build that produces the scores.
  • Default Test Settings: This benchmark passes no test duration or iteration options, so PassMark's defaults apply: in production output, one iteration at the Medium test duration. This benchmark runs it once, with no repetitions.
  • Number of Test Processes: PassMark chooses how many test processes to run; this benchmark does not set it. On aws/a1.2xlarge (8 vCPUs), PassMark ran eight processes.
  • Exit Status: The exit status is that of printing the results file, not of PassMark. A run that writes no results file exits with an error, but a failed PassMark run that still writes the file exits with status 0.

Usage​

Run the image via Docker, and save the results file from stdoutstdoutThe standard output stream of a process, one of the three standard streams with stdin and stderr. Programs write their results to it; a shell can redirect it to a file or another program, such as > results.jsonl, while logs on stderr still reach the terminal.WikipediaGlossary:

docker run --rm --privileged ghcr.io/sparecores/benchmark-passmark:main > results.yml

The harnessharnessThe code that runs a benchmark tool. It prepares the inputs, starts the tool with fixed settings, often several times or in parallel, checks and collects the tool's output, and prints the results in one format. Its settings, not the tool's defaults, decide what the benchmark measures.WikipediaGlossary runs PassMark at the highest scheduling priority (nice -n -20niceA Unix command that runs a program with a changed scheduling priority, from -20 (highest) to 19 (lowest). Raising a process's priority above the default needs the CAP_SYS_NICE capability, which root has.man pageGlossary), which needs the CAP_SYS_NICE capability that --privileged grants. Production runs the container the same way and also sets host networking (--network host).

The container entrypointcontainer entrypointThe executable that a container image runs when a container starts, set by the ENTRYPOINT instruction of its Dockerfile. The image's default command (CMD), or the arguments given after the image name in docker run, are passed to it as arguments, so an entrypoint can wrap any command, for example to set up the environment or record resource usage first. The docker run --entrypoint option replaces it.Dockerfile referenceGlossary runs this benchmark under resource-trackerresource-trackerAn open-source Spare Cores tool that runs a command and samples resource usage while it runs, such as CPU, memory, disk, network, GPU, and GPU memory use. It can optionally stream the samples to the Spare Cores Sentinel platform, so that a run can be checked to see its aggregated and detailed resource utilization, e.g., whether it used all CPU or GPU cores as intended while running a Navigator benchmark workload.resource-tracker on GitHubGlossary, which samples resource usage during the run. Its data is not published.

The image is built for amd64 and arm64. A run took about 3 minutes on aws/a1.2xlarge (production run). Production allows up to 1 hour, because PassMark can be slow on some servers.

Settings​

This benchmark reads no environment variables or command-line options. The suite selection depends only on the available memory (see Workload), and PassMark's own test settings are left at their defaults.

Results​

This benchmark prints PassMark's YAMLYAML: YAML Ain't Markup LanguageA human-readable text format for structured data, built from indented key-value mappings and lists. It is a superset of JSON, and is widely used for configuration files and for exchanging data between programs.YAML specificationGlossary results file to stdout, with the CPU MarkCPU MarkThe overall CPU score of PassMark PerformanceTest. It combines the results of the CPU tests, such as integer and floating-point math, prime numbers, sorting, encryption, compression, physics, and a single-threaded test, into one unitless number, where higher is better. PassMark Software publishes CPU Mark results submitted by users for thousands of processors.PassMark CPU BenchmarksGlossary in Results.SUMM_CPU and the Memory MarkMemory MarkThe overall memory score of PassMark PerformanceTest. It combines the results of the memory tests, such as database operations, cached and uncached reads, writes, and latency, into one unitless number, where higher is better.PassMark Memory BenchmarksGlossary in Results.SUMM_ME. See Results for the file's top-level keys and the individual test results the Navigator publishes, with their units.

PassMark Version​

PassMark publishes no versioned download URLsURL: Uniform Resource LocatorThe address of a resource on the web or a network, such as https://sparecores.com/, made of a scheme, a host, and a path.Glossary, so the image downloads the current release from passmark.com at build time. Production results come from two builds of PassMark PerformanceTest for Linux 11.0, 1002 and 1004; check Version.Build in the output to see which build produced a result.

We treat scores from these two builds as comparable. The PerformanceTest version history lists no CPU or memory test changes in builds 1003 and 1004, but it covers PerformanceTest for Windows; PassMark publishes no version history for the Linux builds.

Workload​

This benchmark runs one workload: PassMark's CPU and memory suites, in PassMark's unattended mode. passmark.sh runs the following steps:

  1. Read the available memory in MiB from free -m.
  2. Start pt_linux under nice -n -20niceA Unix command that runs a program with a changed scheduling priority, from -20 (highest) to 19 (lowest). Raising a process's priority above the default needs the CAP_SYS_NICE capability, which root has.man pageGlossary, with the suites chosen by available memory:
    • 512 MiB or more: pt_linux -r 3, both the CPU and memory suites.
    • Below 512 MiB: pt_linux -r 1, the CPU suite only. No cloud server has less than 512 MiB of memory, so in practice production runs both suites.
  3. Wait for PassMark to finish, then print its results file to stdoutstdoutThe standard output stream of a process, one of the three standard streams with stdin and stderr. Programs write their results to it; a shell can redirect it to a file or another program, such as > results.jsonl, while logs on stderr still reach the terminal.WikipediaGlossary.

The Dockerfile sets TERM=xterm, because PassMark expects a terminal. PassMark writes the results file to the container's working directory.

References​

See References for the terms specific to this image. See the contributor guide for building the image.