StarPU Handbook
Building and Installing StarPU

Installing a Binary Package

One of the StarPU developers being a Debian Developer, the packages are well integrated and very uptodate. To see which packages are available, simply type:

$ apt-cache search starpu

To install what you need, type for example:

$ sudo apt-get install libstarpu-1.3 libstarpu-dev

Installing from Source

StarPU can be built and installed by the standard means of the GNU autotools. The following chapter is intended to briefly remind how these tools can be used to install StarPU.

Optional Dependencies

The hwloc ( topology discovery library is not mandatory to use StarPU but strongly recommended. It allows for topology aware scheduling, which improves performance. libhwloc is available in major free operating system distributions, and for most operating systems.

If libhwloc is installed in a standard location, no option is required, it will be detected automatically, otherwise --with-hwloc=<directory> should be used to specify its location.

If libhwloc is not available on your system, the option --without-hwloc should be explicitely given when calling the configure script.

Getting Sources

StarPU's sources can be obtained from the download page of the StarPU website (

All releases and the development tree of StarPU are freely available on Inria's gforge under the LGPL license. Some releases are available under the BSD license.

The latest release can be downloaded from the Inria's gforge ( or directly from the StarPU download page (

The latest nightly snapshot can be downloaded from the StarPU gforge website (

$ wget

And finally, current development version is also accessible via git. It should only be used if you need the very latest changes (i.e. less than a day old!).

$ git clone

Configuring StarPU

Running is not necessary when using the tarball releases of StarPU. However when using the source code from the git repository, you first need to generate the configure scripts and the Makefiles. This requires the availability of autoconf and automake >= 2.60.

$ ./

You then need to configure StarPU. Details about options that are useful to give to configure are given in Compilation Configuration.

$ ./configure

If configure does not detect some software or produces errors, please make sure to post the contents of the file config.log when reporting the issue.

By default, the files produced during the compilation are placed in the source directory. As the compilation generates a lot of files, it is advised to put them all in a separate directory. It is then easier to cleanup, and this allows to compile several configurations out of the same source tree. To do so, simply enter the directory where you want the compilation to produce its files, and invoke the configure script located in the StarPU source directory.

$ mkdir build
$ cd build
$ ../configure

By default, StarPU will be installed in /usr/local/bin, /usr/local/lib, etc. You can specify an installation prefix other than /usr/local using the option –prefix, for instance:

$ ../configure --prefix=$HOME/starpu

Building StarPU

$ make

Once everything is built, you may want to test the result. An extensive set of regression tests is provided with StarPU. Running the tests is done by calling make check. These tests are run every night and the result from the main profile is publicly available (

$ make check

Installing StarPU

In order to install StarPU at the location which was specified during configuration:

$ make install

Libtool interface versioning information are included in libraries names (, and

Setting up Your Own Code

Setting Flags for Compiling, Linking and Running Applications

StarPU provides a pkg-config executable to obtain relevant compiler and linker flags. As compiling and linking an application against StarPU may require to use specific flags or libraries (for instance CUDA or libspe2).

If StarPU was not installed at some standard location, the path of StarPU's library must be specified in the environment variable PKG_CONFIG_PATH to allow pkg-config to find it. For example if StarPU was installed in $STARPU_PATH:


The flags required to compile or link against StarPU are then accessible with the following commands:

$ pkg-config --cflags starpu-1.3  # options for the compiler
$ pkg-config --libs starpu-1.3    # options for the linker

Note that it is still possible to use the API provided in the version 1.0 of StarPU by calling pkg-config with the starpu-1.0 package. Similar packages are provided for starpumpi-1.0 and starpufft-1.0. It is also possible to use the API provided in the version 0.9 of StarPU by calling pkg-config with the libstarpu package. Similar packages are provided for libstarpumpi and libstarpufft.

Make sure that pkg-config –libs starpu-1.3 actually produces some output before going further: PKG_CONFIG_PATH has to point to the place where starpu-1.3.pc was installed during make install.

Also pass the option –static if the application is to be linked statically.

It is also necessary to set the environment variable LD_LIBRARY_PATH to locate dynamic libraries at runtime.


When using a Makefile, the following lines can be added to set the options for the compiler and the linker:

CFLAGS          +=      $$(pkg-config --cflags starpu-1.3)
LDFLAGS         +=      $$(pkg-config --libs starpu-1.3)

Integrating StarPU in a Build System

Integrating StarPU in a CMake Build System

This section shows a minimal example integrating StarPU in an existing application's CMake build system.

Let's assume we want to build an executable from the following source code using CMake:

#include <starpu.h>
int main(void)
int ret;
ret = starpu_init(NULL);
if (ret != 0)
return 1;
return 0;

The CMakeLists.txt file below uses the Pkg-Config support from CMake to autodetect the StarPU installation and library dependences (such as libhwloc) provided that the PKG_CONFIG_PATH variable is set, and is sufficient to build a statically-linked executable. This example has been successfully tested with CMake 3.2, though it may work with earlier CMake 3.x versions.

{File CMakeLists.txt}
cmake_minimum_required (VERSION 3.2)
project (hello_starpu)
pkg_check_modules(STARPU REQUIRED starpu-1.3)
include_directories (${STARPU_INCLUDE_DIRS})
link_directories (${STARPU_STATIC_LIBRARY_DIRS})
link_libraries (${STARPU_STATIC_LIBRARIES})
message(FATAL_ERROR "StarPU not found")
add_executable(hello_starpu hello_starpu.c)

The following CMakeLists.txt implements an alternative, more complex strategy, still relying on Pkg-Config, but also taking into account additional flags. While more complete, this approach makes CMake's build types (Debug, Release, ...) unavailable because of the direct affectation to variable CMAKE_C_FLAGS. If both the full flags support and the build types support are needed, the CMakeLists.txt below may be altered to work with CMAKE_C_FLAGS_RELEASE, CMAKE_C_FLAGS_DEBUG, and others as needed. This example has been successfully tested with CMake 3.2, though it may work with earlier CMake 3.x versions.

{File CMakeLists.txt}
cmake_minimum_required (VERSION 3.2)
project (hello_starpu)
pkg_check_modules(STARPU REQUIRED starpu-1.3)
# This section must appear before 'add_executable'
# CFLAGS other than -I
# Static LDFLAGS other than -L
# -L directories
message(FATAL_ERROR "StarPU not found")
add_executable(hello_starpu hello_starpu.c)
# This section must appear after 'add_executable'
# -I directories
target_include_directories(hello_starpu PRIVATE ${STARPU_INCLUDE_DIRS})
# Static -l libs
target_link_libraries(hello_starpu PRIVATE ${STARPU_STATIC_LIBRARIES})

Running a Basic StarPU Application

Basic examples using StarPU are built in the directory examples/basic_examples/ (and installed in $STARPU_PATH/lib/starpu/examples/). You can for example run the example vector_scal.

$ ./examples/basic_examples/vector_scal
BEFORE: First element was 1.000000
AFTER: First element is 3.140000

When StarPU is used for the first time, the directory $STARPU_HOME/.starpu/ is created, performance models will be stored in this directory (STARPU_HOME).

Please note that buses are benchmarked when StarPU is launched for the first time. This may take a few minutes, or less if libhwloc is installed. This step is done only once per user and per machine.

Running a Basic StarPU Application on Microsoft Visual C

Batch files are provided to run StarPU applications under Microsoft Visual C. They are installed in $STARPU_PATH/bin/msvc.

To execute a StarPU application, you first need to set the environment variable STARPU_PATH.

c:\....> cd c:\cygwin\home\ci\starpu\
c:\....> set STARPU_PATH=c:\cygwin\home\ci\starpu\
c:\....> cd bin\msvc
c:\....> starpu_open.bat starpu_simple.c

The batch script will run Microsoft Visual C with a basic project file to run the given application.

The batch script starpu_clean.bat can be used to delete all compilation generated files.

The batch script starpu_exec.bat can be used to compile and execute a StarPU application from the command prompt.

c:\....> cd c:\cygwin\home\ci\starpu\
c:\....> set STARPU_PATH=c:\cygwin\home\ci\starpu\
c:\....> cd bin\msvc
c:\....> starpu_exec.bat ..\..\..\..\examples\basic_examples\hello_world.c
MSVC StarPU Execution
Hello world (params = {1, 2.00000})
Callback function got argument 0000042

Kernel Threads Started by StarPU

StarPU automatically binds one thread per CPU core. It does not use SMT/hyperthreading because kernels are usually already optimized for using a full core, and using hyperthreading would make kernel calibration rather random.

Since driving GPUs is a CPU-consuming task, StarPU dedicates one core per GPU.

While StarPU tasks are executing, the application is not supposed to do computations in the threads it starts itself, tasks should be used instead.

TODO: add a StarPU function to bind an application thread (e.g. the main thread) to a dedicated core (and thus disable the corresponding StarPU CPU worker).

Enabling OpenCL

When both CUDA and OpenCL drivers are enabled, StarPU will launch an OpenCL worker for NVIDIA GPUs only if CUDA is not already running on them. This design choice was necessary as OpenCL and CUDA can not run at the same time on the same NVIDIA GPU, as there is currently no interoperability between them.

To enable OpenCL, you need either to disable CUDA when configuring StarPU:

$ ./configure --disable-cuda

or when running applications:

$ STARPU_NCUDA=0 ./application

OpenCL will automatically be started on any device not yet used by CUDA. So on a machine running 4 GPUS, it is therefore possible to enable CUDA on 2 devices, and OpenCL on the 2 other devices by doing so:

$ STARPU_NCUDA=2 ./application

Benchmarking StarPU

Some interesting benchmarks are installed among examples in $STARPU_PATH/lib/starpu/examples/. Make sure to try various schedulers, for instance STARPU_SCHED=dmda.

Task Size Overhead

This benchmark gives a glimpse into how long a task should be (in ┬Ás) for StarPU overhead to be low enough to keep efficiency. Running generates a plot of the speedup of tasks of various sizes, depending on the number of CPUs being used.


Data Transfer Latency

local_pingpong performs a ping-pong between the first two CUDA nodes, and prints the measured latency.

Matrix-Matrix Multiplication

sgemm and dgemm perform a blocked matrix-matrix multiplication using BLAS and cuBLAS. They output the obtained GFlops.

Cholesky Factorization

cholesky_* perform a Cholesky factorization (single precision). They use different dependency primitives.

LU Factorization

lu_* perform an LU factorization. They use different dependency primitives.

Simulated benchmarks

It can also be convenient to try simulated benchmarks, if you want to give a try at CPU-GPU scheduling without actually having a GPU at hand. This can be done by using the simgrid version of StarPU: first install the simgrid simulator from (we tested with simgrid 3.11, 3.12 and 3.13, other versions may have compatibility issues), then configure StarPU with --enable-simgrid and rebuild and install it, and then you can simulate the performance for a few virtualized systems shipped along StarPU: attila, mirage, idgraf, and sirocco.

For instance:

$ export STARPU_PERF_MODEL_DIR=$STARPU_PATH/share/starpu/perfmodels/sampling
$ export STARPU_HOSTNAME=attila
$ $STARPU_PATH/lib/starpu/examples/cholesky_implicit -size $((960*20)) -nblocks 20

Will show the performance of the cholesky factorization with the attila system. It will be interesting to try with different matrix sizes and schedulers.

Performance models are available for cholesky_*, lu_*, *gemm, with block sizes 320, 640, or 960 (plus 1440 for sirocco), and for stencil with block size 128x128x128, 192x192x192, and 256x256x256.