![]() |
Taskflow
3.2.0-Master-Branch
|
To build the benchmark code, enable the CMake option TF_BUILD_BENCHMARKS
to ON
as follows:
After you successfully build the benchmark code, you can find all benchmark instances in the benchmarks/
folder. You can run the executable of each instance in the corresponding folder.
You can display the help message by giving the option --help
.
We currently implement the following instances that are commonly used by the parallel computing community to evaluate the system performance.
Instance | Description |
---|---|
binary_tree | traverses a complete binary tree |
black_scholes | computes option pricing with Black-Shcoles Models |
graph_traversal | traverses a randomly generated direct acyclic graph |
linear_chain | traverses a linear chain of tasks |
mandelbrot | exploits imbalanced workloads in a Mandelbrot set |
matrix_multiplication | multiplies two 2D matrices |
mnist | trains a neural network-based image classifier on the MNIST dataset |
parallel_sort | sorts a range of items |
reduce_sum | sums a range of items using reduction |
wavefront | propagates computations in a 2D grid |
linear_pipeline | pipeline scheduling on a linear chain of pipes |
graph_pipeline | pipeline scheduling on a graph of pipes |
We implement consistent options for each benchmark instance. Common options are:
option | value | function |
---|---|---|
-h | none | display the help message |
-t | integer | configure the number of threads to run |
-r | integer | configure the number of rounds to run |
-m | string | configure the baseline models to run, tbb, omp, or tf |
You can configure the benchmarking environment by giving different options.
In addition to a Taskflow-based implementation for each benchmark instance, we have implemented two baseline models using the state-of-the-art parallel programming libraries, OpenMP and Intel TBB, to measure and evaluate the performance of Taskflow. You can select different implementations by passing the option -m
.
You can configure the number of threads to run a benchmark instance by passing the option -t
. The default value is one.
Depending on your environment, you may need to use taskset
to set the CPU affinity of the running process. This allows the OS scheduler to keep process on the same CPU(s) as long as practical for performance reason.
Each benchmark instance evaluates the runtime of the implementation at different problem sizes. Each problem size corresponds to one iteration. You can configure the number of rounds per iteration to average the runtime.