Skip to main content

Glossary

Acronyms and terms used on this image's pages. See the site-wide glossary for all terms.

A​

AMD64​

The 64-bit version of the x86 instruction set architecture, introduced by AMD in 2003 and also implemented by Intel, which runs most cloud servers. Linux distributions and Docker name it amd64 or x86_64. See Wikipedia.

C​

container entrypoint​

The 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. See Dockerfile reference.

CPU​

Central Processing Unit: The general-purpose processor of a computer, which runs the operating systemOS: operating systemThe software that manages a computer's hardware and runs programs on it, such as Linux or Windows. A cloud server runs the OS of the image it was started from.Glossary and programs. A CPU has one or more physical cores, and with SMT each core runs two or more hardware threads. See Wikipedia.

CPU-credit throttling​

A limit on burstable cloud server types, which earn CPU credits while they run below a baseline CPU usage and spend them to run above it. When the credits run out, the provider throttles the server to its baseline, so sustained load runs slower than a short burst. See AWS burstable instances.

I​

I/O​

Input/Output: The transfer of data between a computer and the outside world, such as reading and writing disks or sending and receiving network packets. A workload limited by its speed rather than by the CPU is called I/O-bound. See Wikipedia.

J​

JSON​

JavaScript Object Notation: A text format for structured data, built from objects (key-value pairs), arrays, strings, numbers, booleans, and null. Most languages and tools read and write it, which makes it a common format for APIAPI: Application Programming InterfaceA defined set of requests and responses through which one program uses another, such as a web service's HTTP endpoints or a library's functions.WikipediaGlossary responses and benchmark output. See JSON.

N​

nested paging​

Hardware support for memory virtualization, in which the CPU translates a guest's virtual addresses through the guest's page tables and then through a second set of page tables kept by the hypervisor. It removes the need for the hypervisor to maintain shadow page tables, but a TLB miss then needs more memory lookups. Intel calls it Extended Page Tables and AMD Rapid Virtualization Indexing. See Wikipedia.

nice​

A 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. See man page.

P​

psutil​

A cross-platform Python library for retrieving information on running processes and system utilization, such as CPU, memory, disks, and network. It can count both logical CPUs and physical cores. See psutil docs.

R​

resource-tracker​

An open-source Spare Cores tool that runs a command and samples resource usage while it runs, such as CPU, memory, disk, network, 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, 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. See resource-tracker on GitHub.

S​

SCore​

Spare Cores score: A CPU speed score of a server type in Spare Cores Navigator, used to compare the speed of server types. It is measured with the cpu stressor of stress-ng at increasing worker counts. The single-core SCore is the result with one worker; the multi-core SCore, the raw multi-core CPU speed that SCore means on its own, is the highest result.

shared-core​

Describes a cloud server type whose vCPUs share physical cores with other servers, often with a guaranteed baseline of only a fraction of a core. Such server types are cheaper, but their CPU performance can vary with the load of neighboring servers or be limited by CPU credits. See Google Cloud shared-core machine types.

SIMD​

Single Instruction, Multiple Data: A form of parallel processing in which one CPU instruction applies the same operation to several data elements at once. CPUs implement it with vector instruction set extensions, which x86 and Arm CPUs both provide. See Wikipedia.

SMT​

Simultaneous Multithreading: A CPU technique that runs two (or more) hardware threads on one physical core, sharing its execution units, e.g. Intel Hyper-Threading. It raises throughput when a thread stalls, but the threads compete for the core. Cloud vendors usually sell each thread as a vCPU. See Wikipedia.

stderr​

The standard error stream of a process, one of the three standard streams with stdin and stdout. Programs write logs, progress, and error messages to it, so that they stay separate from the output on stdout when the output is redirected to a file or another program. See Wikipedia.

stdout​

The 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. See Wikipedia.

stress-ng​

An open-source tool that loads a computer in selectable ways, with hundreds of stress tests (stressors) that exercise the CPU, memory, file systems, and kernel interfaces. With --metrics, it reports each stressor's throughput in bogo ops/s. See stress-ng on GitHub.

stress-ng bogo ops/s​

bogus operations per second: The throughput metric of stress-ng: how many times a stressor completes its own unit of work per second. Each stressor defines that unit differently, so the values compare only within one stressor and one stress-ng version. See stress-ng man page.

stress-ng div16 method​

A method of the stress-ng cpu stressor, selected with --cpu-method div16, in which each operation runs 50,000 16-bit unsigned integer divisions. Integer division takes many CPU cycles and depends little on memory, so it loads the core's arithmetic units directly. See stress-ng man page.

stress-ng metrc line​

A line in which stress-ng --metrics prints a stressor's results when the run ends, tagged metrc: the bogo ops count, the real, user, and system time, and the bogo ops/s, among other columns. See stress-ng man page.

stress-ng stressor​

One stress test of stress-ng, such as cpu, memcpy, or fork, selected with a command-line option of the same name and run by one or more worker processes. See stress-ng man page.

T​

TLB​

Translation Lookaside Buffer: A CPU cache of recent translations from virtual to physical memory addresses. A TLB shootdown invalidates entries on other cores after a mapping changes, which needs an interrupt to each of them. See Wikipedia.

V​

vCPU​

virtual CPU: A 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. See Wikipedia.

VM​

virtual machine: A computer emulated in software on a physical host, with its own OSOS: operating systemThe software that manages a computer's hardware and runs programs on it, such as Linux or Windows. A cloud server runs the OS of the image it was started from.Glossary and a share of the host's CPUs, memory, and storage. Most cloud servers are VMs. See Wikipedia.

VM exit​

A transition from a virtual machine's guest code to the hypervisor, triggered by an operation the hypervisor has to handle, such as some privileged instructions, I/O, or interrupts. Each exit and return costs CPU time, so workloads that cause many exits run slower in a VM.