Discourse keeps changing, can we freeze the version of discourse bench


@tgxworld we keep doing perf work on Discourse, at the moment it is totally unclear what version of Discourse the actual benches are on.

Can we

  • Freeze the version somehow for benchmarking purposes
  • Have a “hash” of the discourse git commit used as the key for the benchmarking results (so we can update the bench later on)
  • Ensure we never mix results in the site from differing discourse commits.


We’re freezing it to ruby-bench-docker/runner at master · ruby-bench/ruby-bench-docker · GitHub.

For the other two points, I’ll have to look into that.