Skip to content
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Futhark implementations of various benchmarks. The intention is that these implementations are of existing published benchmarks, and thus show where we do well or poorly. We highly encourage everyone to make use of it when evaluating Futhark performance. The following contains instructions on how to do that.

Running benchmarks

The recommended method for running all benchmarks is

futhark bench * --backend=opencl --ignore-files /lib/

This uses the opencl backend, and ignores the test suites of any embedded libraries (which are usually too small to be useful benchmarks, and would merely be noise). You can replace opencl with another backend. While the c backend is likely too slow to be practical for many of the benchmarks, the cuda backend should perform fine.

You can also add --ignore-files /micro/ to ignore the microbenchmarks of single language constructs, which are often not very interesting, but do take a long time to run.

If necessary, you can use --pass-option to pass more options to the generated Futhark programs. This may be necessary if you are using the OpenCL backend on a system with more than one OpenCL device, and you wish to use another device than the default. For example, to ask Futhark to use the first device that contains "NVIDIA" in its name, you could use --pass-option=-dNVIDIA.

If you wish to analyse the performance results with a program, passing --json=results.json to futhark bench may be useful.

For more information, see the documentation for futhark bench.

Internal details

Many of the input/output files are stored in a simple binary format for performance and space reasons. This format is documented in the Futhark reference manual, and can be converted to a textual representation via the futhark dataset tool.

You can’t perform that action at this time.