This is a Linux/Unix port of release 2 of BYTE Magazine's BYTEmark benchmark
program (previously known as BYTE's Native Mode Benchmarks). It is designed
to expose the capabilities of a system's CPU, FPU, and memory system.
UnixBench v4.1 based on the BYTE UNIX Benchmarks v3.
This stress test suite will stress a computer system in various
selectable ways It was designed to exercise various physical
subsystems of a computer as well as various operating system kernel
interfaces.
The Benchmark::Forking module changes the behavior of the standard
Benchmark module, running each piece of code to be timed in a separate
forked process. Because each child exits after running its timing loop,
the computations it performs can't propogate back to affect subsequent
test cases.
This can make benchmark comparisons more accurate, because the
separate test cases are mostly isolated from side-effects caused by
the others. Benchmark scripts typically don't depend on those
side-effects, so in most cases you can simply use or require this
module at the top of your existing code without having to change
anything else.
This library provides a powerful but simple way to measure sofware
performance. It provides both a framework for executing and analysing
benchmarks and a set of driver functions that makes it easy to build and
run benchmarks, and to analyse their results.
The Phoronix Test Suite is the most comprehensive testing and benchmarking
platform available for the *nix operating system. This software is designed
to effectively carry out both qualitative and quantitative benchmarks in a
clean, reproducible, and easy-to-use manner.
RAMspeed is a command line utility to measure cache and memory performance of
computer systems. It offers 18 cache and memory benchmarks for i386 and amd64
machines, though 6 only for alpha ones. There are *mark benchmarks such as
INTmark, FLOATmark, MMXmark and SSEmark. They operate with linear (sequential)
data streams passed through ALU, FPU, MMX and SSE units respectively.
There are also *mem benchmarks such as INTmem, FLOATmem, MMXmem and SSEmem.
These are supposed to illustrate how fast is actual read/write memory
performance. There are also non-temporal versions of MMX and SSE benchmarks.
They have been coded with special instructions to minimise cache pollution on
memory reads and to eliminate it completely on memory writes. In addition, they
operate with a built in aggressive data prefetching algorithm. In some cases,
non-temporal MMXmark and SSEmark can deliver almost 100% of theoretical
bandwidth while reading.
This is lmbench-3.0-a9, a (sometimes controversial) system performance
measurement tool. lmbench is a suite of simple, portable, ANSI/C
microbenchmarks for UNIX/POSIX. In general, it measures two key features:
latency and bandwidth. lmbench is intended to give system developers insight
into basic costs of key operations. You can go to /usr/local/lib/lmbench and
do one of the following:
make results (to run the benchmarks)
make rerun (to rerun the benchmarks)
make see (to see how you did)
SysBench is a modular, cross-platform and multi-threaded benchmark tool
for evaluating OS parameters that are important for a system running a
database under intensive load.
The idea of this benchmark suite is to quickly get an impression about
system performance without setting up complex database benchmarks or
even without installing a database at all.
Current features allow to test the following system parameters:
* file I/O performance
* scheduler performance
* memory allocation and transfer speed
* POSIX threads implementation performance
* database server performance (OLTP benchmark)
Primarily written for MySQL server benchmarking, SysBench will be
further extended to support multiple database backends, distributed
benchmarks and third-party plug-in modules.
Iorate is a general purpose storage I/O benchmarking tool.
Iorate was created in 1997 by Vince Westin of EMC while working with Cliff
Burrell of FedEx to fill a need to perform a set of storage I/O benchmarks.
Though Iorate was developed by EMC staff with EMC resources there are no
EMC-specific pieces to the testing, it just tests storage.