Currently, running the performance tests takes a considerable amount of time.
There are some ideas floating around about how we could cut down on the execution time. Each of these (and any additional) ideas should be evaluated for their impact and implemented accordingly.
In no particular order; enumeration provided solely for easier reference:
- because we retry a failed target rate is expensive we might want to change the hillclimber to be biased and not divide the range 50:50 but perhaps 25:75 to decrease the times we miss a target
- we might want to increase the hillClimberMinimumDelta
- we could experiment with using the achieved rate as a guide for the target rate for the next iteration