mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 01:07:18 +03:00
6e48abc793
This should be merged after #6080. This PR adds a patch (and consequently updates the `ci/cron/perf/compare.sh` script) to apply the same logical change as #6080 on top of the baseline commit, so our performance comparison remains "apples to apples". I am well aware that managing patches is not going to be a great way forward. The rate of changes on the benchmark seems to be slow enough that this is good enough for now, but should we change the benchmark more often and/or want to add new benchmarks, a better approach would be to handle the changes at the Scala level. That is: - Create a "rest of the world" (world = Speedy, its compiler, and all of the associated types) interface that benchmarks would depend on, rather than depend directly on the rest of the codebase. - Create two implementations of that interface, one that compiles against the current state of the world, and one that compiles against the baseline. - Change the script to load the relevant implementation, and then run all the benchmarks as-is, with no match necessary. CHANGELOG_BEGIN CHANGELOG_END |
||
|---|---|---|
| .. | ||
| azure-cleanup | ||
| cron | ||
| docker/daml-sdk | ||
| patch_bazel_windows | ||
| build-unix.yml | ||
| build-windows.yml | ||
| check-changelog.sh | ||
| compatibility_ts_libs.yml | ||
| compatibility-windows.yml | ||
| compatibility.yml | ||
| configure-bazel.sh | ||
| dev-env-install.sh | ||
| dev-env-push.py | ||
| postgresql.conf | ||
| report-end.yml | ||
| report-start.yml | ||
| slack_user_ids | ||
| tell-slack-failed.yml | ||
| windows-diagnostics.ps1 | ||