Free benchmark software for linux

Benchmark is a Perl module with benchmark running times of Perl code.

SYNOPSIS

use Benchmark qw(:all) ;

timethis ($count, "code");

# Use Perl code in strings...
timethese($count, {
Name1 => ...code1...,
Name2 => ...code2...,
});

# ... or use subroutine references.
timethese($count, {
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
});

# cmpthese can be used both ways as well
cmpthese($count, {
Name1 => ...code1...,
Name2 => ...code2...,
});

cmpthese($count, {
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
});

# ...or in two stages
$results = timethese($count,
{
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
},
none
);
cmpthese( $results ) ;

$t = timeit($count, ...other code...)
print "$count loops of other code took:",timestr($t),"n";

$t = countit($time, ...other code...)
$count = $t->iters ;
print "$count loops of other code took:",timestr($t),"n";

# enable hires wallclock timing if possible
use Benchmark :hireswallclock;

The Benchmark module encapsulates a number of routines to help you figure out how long it takes to execute some code.

timethis - run a chunk of code several times
timethese - run several chunks of code several times
cmpthese - print results of timethese as a comparison chart
timeit - run a chunk of code and see how long it goes
countit - see how many times a chunk of code runs in a given time

HardInfo is a benchmark tool and system information for Linux systems.
Main features:
Get information about your computer:
- The Processor
- Operating System
- Languages
- Sensors
- Filesystems
- Shared Directories
- Display
- Network Interfaces
Its devices (and what controls them):
- Kernel Modules
- PCI Devices
- USB Devices
- Printers
- Input Devices
- Storage
Benchmark:
- ZLib
- MD5 and SHA1
- And generate nicely-formatted HTML reports!
Enhancements:
- Maintenance version.
- Mostly bugfixes, plugged memory leaks.
- Minor feature enhancements.

bandwidth project is an artificial benchmark for measuring memory bandwidth, useful for identifying a computers weak areas.
It tests several types of memory:
- Main memory read accesses
- Main memory write accesses
- Level 2 cache read accesses
- Level 2 cache write accesses
- Framebuffer read accesses
- Framebuffer write accesses
- String library routines
Enhancements:
- 64-bit support has been added.

Benchmark::Forking is a Perl module to run benchmarks in separate processes.

SYNOPSIS

use Benchmark::Forking qw( timethis timethese cmpthese );

timethis ($count, "code");

timethese($count, {
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
});

cmpthese($count, {
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
});

Benchmark::Forking->enabled(0); # Stop using forking feature
...
Benchmark::Forking->enabled(1); # Begin using forking again

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 cant 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 dont 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. (A few key exceptions are noted in "BUGS".)

The Bioinformatics Benchmark System is an attempt to build a reasonable testing framework, tests, and data, to enable end users and vendors to probe the performance of their systems.

What we are trying to do is to create a framework for testing, and a core set of tests that all may download and use to probe specific elements of systems performance.

Moreover, the source to these tests are available under GPL, and are hosted on Bioinformatics.org and Scalable Informatics LLC The idea is to enable end users, consumers, systems developers, and others to easily build and use meaningful tests for measurement and tuning reasons.

Joe Landman from Scalable Informatics LLC conceived the idea and wrote the original codes. We are looking for additional benchmark code suggestions, tests, data sets, etc.

Current baseline tests are several NCBI BLAST runs, several HMMer runs, and a variety of others. We plan to include ClustalW, X!Tandem, various chemistry, dynamics, and related tests, as well as several others.

Tests such as LINPACK or HPL simply do not provide meaningful performance indicators or predictive models for high performance informatics. Unfortunately, nor do a number of more recent and focused tests.

This is a problem as LINPACK and HPL specifically test the performance on various matrix operations, where you have effectively regular memory access patterns, and specific mathematical operations.

These codes are most useful for comparison to codes with heavy floating point operations, and interleaved memory traffic. These codes were not designed for comprehensive systems benchmarking, where disk I/O, memory latency, and other factors all contribute to the performance issues.

The best tests are the ones that are most similar to the codes you will run on the machine. The tests themselves should be reasonable approximations to a real execution of your code, using real data. You may need to pare it back in order to get realistic run times.

You should have a reasonable subset of data sizes. A single test does not tell you how your system scales, and one of the reasons for the existance of this test is specifically to allow you to test the performance while you increase various aspects of the workload.

You rarely get a quiescent system in a cluster, so we would recommend that you try to run in as realistic an operating environment as possible. A baseline in a quiescent system is fine, but it may set your expectations unreasonably.
top

Procbench is a multiplatform information tool and CPU benchmark for x86 processors. This application tests memory transfer and math capabilities of your x86 processor.
Main features:
- Identification of CPU by CPUID.
- Approximation of CPU MHz.
- Benchmarks.
Installation:
type:
make install
try:
./procbench -h
for information
Enhancements:
- DB of CPUs added.

MBW is a memory bandwidth benchmark program.
MBW determines the "copy" memory bandwidth available to userspace programs. Its simplistic approach models that of real applications. It is not tuned to extremes and it is not aware of hardware architecture, just like your average software package.
Enhancements:
- MBW now runs much faster due to quicker preparation for the tests.
- A new test (memcpy() with arbitrary block size) was added.
- Options to select tests and customize output were added.

XSDBench project is a W3C XML Schema benchmark that compares the performance of validating XML parsers. The following parsers are supported in the latest version:
Apache Xerces-C++ (C++)
CodeSynthesis XSD (C++)
Gnome Libxml2 (C)1
Microsoft XML Core Services (MSXML) (C/C++)
Oracle XDK (C/C++)
Libxml2 is currently disqualified since it cannot handle the benchmark schemas. The benchmark measures validation throughput, statically-linked test executable size, and, where possible, peak heap and stack memory usage during parsing.
Enhancements:
- Results for the following platforms and compilers are available: GNU/Linux on AMD Opteron 244 with GCC 4.1.2, Windows on Intel Pentium 3 with VC++ 7.1, GNU/Linux on Intel Pentium 3 with Intel C/C++ 9.1, GNU/Linux on IBM PowerPC 970MP with IBM XML C/C++ 8.0.