Results 11–20 of 95 for /benchmarks/.(0.019 seconds)
Intel MPI Benchmark
The idea of IMB is to provide a concise set of elementary MPI
benchmark kernels. With one executable, all of the supported
benchmarks, or a subset specified by the command line, can be run.
The rules, such as time measurement (including a repetitive call
of the kernels for better clock synchronization), message lengths,
selection of communicators to run a particular benchmark (inside
the group of all started processes) are program parameters.
NetApps file system benchmark
PostMark is the benchmark used in the NetApp Technical Report TR-3022,
"PostMark: A New File System Benchmark". The paper fully explains how
to use this tool.
From the paper's Abstract:
Existing file system benchmarks are deficient in portraying
performance in the ephemeral small-file regime used by Internet
software, especially:
* electronic mail
* netnews
* web-based commerce
PostMark is a new benchmark to measure performance for this class of
application.
Model-based file system workload generator
Filebench is quick to set up and use unlike many of the commercial
benchmarks which it can emulate. It is also a handy tool for
micro-benchmarking storage subsystems and studying the relationships of
complex applications such as relational databases with their storage
without having to incur the costs of setting up those applications,
loading data and so forth.
Filebench uses loadable workload personalities in a common framework to
allow easy emulation of complex applications upon file systems. The
workload personalities use a Workload Definition Language to define the
workload's model.
Tool for measuring webserver performance
Httperf is a tool for measuring web server performance. It provides a flexible
facility for generating various HTTP workloads and for measuring server
performance.
The focus of httperf is not on implementing one particular benchmark but on
providing a robust, high-performance tool that facilitates the construction of
both micro- and macro-level benchmarks. The three distinguishing characteristics
of httperf are its robustness, which includes the ability to generate and
sustain server overload, support for the HTTP/1.1 and SSL protocols, and its
extensibility to new workload generators and performance measurements.
Automating the process of benchmarking a web server
Autobench is a simple Perl script for automating the process of benchmarking
a web server (or for conducting a comparative test of two different web
servers). The script is a wrapper around httperf. Autobench runs httperf a
number of times against each host, increasing the number of requested
connections per second on each iteration, and extracts the significant data
from the httperf output, delivering a CSV or TSV format file which can be
imported directly into a spreadsheet for analysis/graphing.
Performance Test of Filesystem I/O
Blogbench is a portable filesystem benchmark that tries to reproduce the
load of a real-world busy file server.
It stresses the filesystem with multiple threads performing random reads,
writes and rewrites in order to get a realistic idea of the scalability
and the concurrency a system can handle.
Performance Test of Filesystem I/O
Bonnie++ is a benchmark suite that is aimed at performing a number of
simple tests of hard drive and file system performance. Then you can
decide which test is important and decide how to compare different
systems after running it. I have no plans to ever have it produce a
single number, because I don't think that a single number can be useful
when comparing such things.
The main program tests database type access to a single file (or a set
of files if you wish to test more than 1G of storage), and it tests
creation, reading, and deleting of small files which can simulate the
usage of programs such as Squid, INN, or Maildir format email.
Performance Test of Filesystem I/O
Bonnie: Filesystem Benchmark Program
Bonnie tests the speed of file I/O using standard C library calls.
It does reads and writes of blocks, testing for the limit of sustained
data rate (usually limited by the drive or controller) and updates on
a file (better simulating normal operating conditions and quite dependent
on drive and OS optimisations).
The per-character read and write tests are generally limited by CPU speed
only on current-generation hardware. It takes some 35 SPECint92 to read
or write a file at a rate of 1MB/s using getc() and putc().
The seek tests are dependent on the buffer cache size, since the fraction
of disk blocks that fits into the buffer cache will be found without any
disk operation and will contribute zero seek time readings. I.e. if the
buffer cache is 16MB and the Bonnie test file is 32MB in size, then the
seek time will come out as half its real value. The seek time includes
rotational delay, and will thus always come out higher than specified for
a drive.
Benchmarking tool for pipes
Cpipe copies its standard input to its standard output while measuring the time
it takes to read an input buffer and write an output buffer. Statistics of
average throughput and the total amount of bytes copied are printed to the
standard error output.
Benchmarking tool to measure peak capabilities of opencl devices
clpeak
a synthetic benchmarking tool to measure peak capabilities of opencl devices
A synthetic benchmarking tool to measure peak capabilities of opencl devices.
It only measures the peak metrics that can be achieved using vector operations
and does not represent a real-world use case