Version 96 (modified by benl, 3 years ago) (diff)


Status of DPH Benchmarks

Benchmarking results last updated on: 3nd December 2010.

This page gives an overview of how well the benchmarks in the dph-examples/ directory of package dph are currently working.

The benchmarks are run each night by DPH BuildBot. The results are posted to cvs-ghc and uploaded to Check there for the latest numbers.


  • Running debug threaded programs with heap profiling triggers an assertion in the RTS. Running them without debugging is a segfault.
  • QuickHull: vectorised.par.N1 version is 6x slower than the immutable Data.Vector version in absolute terms.
  • QuickSort: vectorised.seq version doesn't compile due to a blow-up in SpecConstr.
  • SMVM: runs 1000x slower than the C program with small matrix sizes. For 1000x1000 with 10% fill ratio it takes about 1s and allocates 400M memory, while the C program is instantaneous. For larger sizes it dies with OOM.
  • BarnesHut: builds but runs very slowly. The immediate problem is that some dictionaries are recursive, their methods don't inlined, so fusion doesn't work.


  • Benchmarks are currently being run with -fasm, and not via the LLVM backend. This will affect comparisons with C, but not with Data.Vector as it uses the same backend.

Flat Parallelism

Flat parallel programs are ones in which parallel computations do not invoke further parallel computations. For Repa, this means that the value of each element in a given array can be computed independently of the others. These should run as fast as equivalent programs using immutable Data.Vector. We'd also hope to get close to the performance of C programs using equivalent algorithms, though this is a harder comparison due to differences in the back-end code generator.

Matrix-Matrix multiplication. Size=1024x1024.

name runtime speedup efficiency notes
repa.mmult.c.seq 3.792s 1 1 A
repa.mmult.par.N1 8.484s 0.45 0.45
repa.mmult.par.N4 2.147s 1.77 0.44
repa.mmult.par.N8 1.097s 3.46 0.43

A: Straightforward C program using triple nested loops. A cache-friendly block-based version would be faster.

Status: Ok, but about 20% slower than in 6.13.
ToDo: Run with LLVM and without bounds checking.

Solves the Laplace equation in the 2D plane. Size=400x400.

name runtime speedup efficiency notes
repa.laplace.c.seq 1.299s 1 1 A
repa.laplace.par.N1 9.405s 0.14 0.14
repa.laplace.par.N4 2.521s 0.51 0.13
repa.laplace.par.N8 2.124s 0.61 0.08

A: Straightforward C program using triple nested loops. A cache-friendly block-based version would be faster.

Status: Too slow. We should check this again with LLVM.
ToDo: Run with LLVM and without bounds checking. Run with more threads to see if we can get back to the C version's run time.

Applies a Gaussian blur filter to a 2D image. Size=512x512.

name runtime speedup efficiency notes
repa.blur.par.N1 2.620s 1 -
repa.blur.par.N4 0.717s 3.65 -
repa.blur.par.N8 0.414s 6.33 -

ToDo: Runs ok, but need other versions for comparison.

Performs Canny edge detection to a 2D image. Size=512x512.

name runtime speedup efficiency notes
repa.edgedetect.par.N1 206ms 1 -
repa.edgedetect.par.N4 79ms 2.6 -
repa.edgedetect.par.N8 55ms 3.75 -

ToDo: Runs ok, but need other versions for comparison.

Performs high-pass filtering using 2D and 3D FFTs. These are naive benchmarks used for regression testing only. They divide right down to (rank generalise) two-point vectors and construct the result using copying append. Using an inplace algorithm (like with FFTW) would be significantly faster.

ToDo: Runs ok, but need other versions for comparison.

Statically Nested Parallelism

Statically nested parallelism is where the parallelism has a fixed, finite depth. For example mapP f (filterP g xs). Statically nested programs are easier to vectorise than dynamically nested programs. At present, single threaded statically nested programs should run as fast as equivalent Data.Vector programs. Parallel versions should display a good speedup.

Computes the sum of the squares from 1 to N using Int. N = 100M.
name runtime speedup efficiency notes
dph.sumsq.vector.seq.N4 404ms 1 1
dph.sumsq.vectorised.seq.N4 434ms 0.93
dph.sumsq.vectorised.par.N1 443ms 0.91 0.91
dph.sumsq.vectorised.par.N2 222ms 1.82 0.91
dph.sumsq.vectorised.par.N4 111ms 3.63 0.91
dph.sumsq.c.seq 116ms 3.48

Status: fine

Computes the dot product of two vectors of Doubles. N=10M.

name runtime speedup efficiency notes
dph.dotp.vector.seq.N4 68ms 1 1
dph.dotp.vectorised.seq.N4 58ms 1.17 A
dph.dotp.vectorised.par.N1 55ms 1.24 1.24 B
dph.dotp.vectorised.par.N2 33ms 2.06 1.03
dph.dotp.vectorised.par.N4 25ms 2.72 0.68
dph.dotp.c.seq 45ms 1.35

A: The core for the vectorised.seq version is equivalent to the vector version. We expect the backend has compiled it differently. Check this again with LLVM.
B: The vectorised.par version runs faster than vectorised.seq because the latter has a duplicate counter in the inner loop. We need a duplicate-loop-counter removal optimisation.

Status: fine

Takes the even valued Ints from a vector. N=10M.

name runtime speedup efficiency notes
dph.evens.vector.seq.N4 98ms 1 1
dph.evens.vectorised.seq.N4 174ms 0.56
dph.evens.vectorised.par.N1 182ms 0.53 0.56
dph.evens.vectorised.par.N2 106ms 0.92 0.46
dph.evens.vectorised.par.N4 80ms 1.23 0.30 A
dph.evens.c.seq 31ms 3.16

A : Benchmark is totally memory bound, so we're not expecting to see much speedup.

Status: ok, but run again with LLVM to see if that fixes the slowdown wrt C.

Multiplies a dense vector with a sparse matrix represented in the compressed sparse row format (CSR).

Status: Runs on 1000x1000 matrices with 10% fill ratio, but about 1000x slower than the C program. Dies with OOM for 2000x2000. Segfaults with 10000x10000.

Dynamically Nested Parallelism

Dynamically nested programs have a recursive structure where each level of the recursion invokes more parallel computations. This is common for benchmarks that use divide-and-conquer style algorithms.

The Sieve of Eratosthenes using parallel writes into a sieve structure represented as an array of Bools.

Todo: We currently don't have a proper parallel implementation of this benchmark, as we are missing a parallel version of default backpermute. This needs a parallel update operation, but we currently can't guarantee atomic updates of compound types such as tuples.

Sort a vector of doubles by recursively splitting it and sorting the two halves. This is a naive benchmark used for regression testing only. We divide right down to two-point vectors and construct the result using copying append. A production algorithm would switch to an in-place sort once the size of the vector reaches a few thousand elements. N=100k.

name runtime speedup efficiency notes
dph.quicksort.vectorised.par.N1 428ms 1 1
dph.quicksort.vectorised.par.N2 417ms 1.02
dph.quicksort.vectorised.par.N4 422ms 1.01

Status: Sequential vectorised version does not compile due to a blowup in SpecConstr.

Quickhull (SLOWLORIS)
Given a set of points in the plane, compute the sequence of points that encloses all points in the set. This benchmark is interesting as it is the simplest code that exploits the ability to implement divide-and-conquer algorithms with nested data parallelism. N=1M.

name runtime speedup efficiency notes
dph.quickhull.vector-immutable.seq.N4 0.166s 1 1
dph.quickhull.vectorised.seq.N4 0.677s 0.24 4x slower
dph.quickhull.vectorised.par.N1 1.033s 0.16 0.16 6x slower
dph.quickhull.vectorised.par.N2 0.686s 0.24 0.12
dph.quickhull.vectorised.par.N4 0.571s 0.29 0.07
dph.quickhull.vector-mutable.seq.N4 0.086s 1.93 A
dph.quickhull.vector-forkIO.par.N4 0.064s 2.59 0.65 B
dph.quickhull.c.seq 0.044s 3.77 C

A: Uses mutable Data.Vectors for intermediate buffers.
B: Uses mutable Data.Vectors, forkIO and atomicModifyIORef. Concurrent threads fill a shared output vector. Code is uglier than the C version.
C: Sequential C version with pre-allocated mutable intermediate buffers.

Status: Benchmark scales but single threaded vectorised.par version is 6x slower than version using immutable Data.Vectors. QuickHull is based around filtering operations, so the fact that Evens is also slow is probably related.

Dynamically Nested Parallelism with Algebraic Data Types

These programs also use user defined algebraic data types. Vectorization of these programs is still a work in progress.

Words (BROKEN)
Counts the number of words in a string. This is a naive divide-and-conquer benchmark that divides right down to a single character. A production program would switch to a simple sequential algorithm once the string chunks were small enough. It's a good stress test for the vectoriser though.

Status: Sequential vectorised version does not compile due to blowup in SpecConstr.
Todo: Generate some larger test data. Right now it's just got a small test string baked into the program.

This benchmark implements the Barnes-Hut algorithm to solve the n-body problem in two dimensions. There is a naive O(n2) version in the same package.

name runtime speedup efficiency notes
dph.nbody.vector.seq.N4 100ms 1 A
dph.nbody.vectorised.seq.N4 4681ms ~50x slower
dph.nbody.vectorised.par.N1 2381ms ~25x slower

A : Time stated is end-to-end, not just for the kernel.

Status: Compiles, but fusion doesn't work so it's very slow.
ToDo: Make the vectorised version give the same output as the vector version. The benchmark setup is a bit different. Fixing this won't cause a 50x speed difference though.




  • vectorised means it's been through the DPH vectorising transform.
  • vector is a hand written version using immutable Data.Vectors
  • vector-mutable is a hand written version using mutable Data.Vectors.
  • vector-immutable means the same as vector and is used when there is also an mutable version.


  • Whether a benchmark is natively parallel or sequential.
  • Parallel versions are also run single threaded (with -N1) and sequential versions are also run with (-N4) so we get the parallel GC.
  • Parallel versions with -N1 will tend to be slower than natively sequential versions due to overheads for supporting parallelism.


  • Value passed to Haskell Runtime with -N threads flag.
  • Number of Haskell Execution Contexts (HECs) used when running the benchmark.
  • Can be less than the number of hardware threads / cores in the physical machine.


  • Runtime of reference / runtime of benchmark.
  • Measures how much faster a benchmark is relative to the reference.

(relative) efficiency

  • Speedup / number of threads.
  • Indicates the communication overhead involved with running something in parallel.
  • Can be > 1 if the parallel version running with a single thread is faster than the sequential reference version.


  • BROKEN: Benchmark doesn't compile, or crashes when run.
  • SLOWDOWN: Benchmark gets slower as number of threads increases.
  • SLOWLORIS: Benchmark scales as the number of threads increases, but the absolute performance is not acceptable compared with equivalent versions using immutable Data.Vectors. We do not have a setup in which the parallel version runs faster than the sequential reference version. Cute, but too slow to be useful.

Benchmark machine

  • 2x 3.0GHz Quad-Core Intel Xeon 5400
  • 12MB (2x6MB) on-die L2 cache per processor
  • independent 1.6GHz frontside bus per processor
  • 800MHz DDR2 FB-DIMM
  • 256-bit-wide memory architecture
  • Mac OS X Server 10.5.6