The controller can be configured in more detail using the config.yaml file that can be mounted to the platform controller container as described in the Volumes section.

Benchmark-specific timeouts

For single benchmarks, the timouts can be configured in the following way

  '': # benchmark URL
    benchmark: 2400000 # in ms
    challenge: 2400000 # in ms

For every benchmark, there can be two timeouts. One for the benchmark when it is executed in the “normal” way and a second timeout for the benchmark when it is used for a challenge.