Improve backend benchmarking interface
Use by system administrators only.
Submitted by Elmer van Chastelet on 4 July 2023 at 14:07
Construction of the dataset to be used for benchmarking has improved, by distributing the submissions evenly over the selection of programming environments (if #envs>1 and when possible).
Timing information now contains all needed information about the last job started (and timed). It no longer uses hard-coded programs as last job, but uses one from the dataset instead.