You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 2, 2021. It is now read-only.
Improve hist benchmarks driver and add to CI (#770)
* Remove hardcoded --stack-yaml and upstream/master assumption
* support Cabal in bench suite
* add benchmark run to CI
Even if the time measurements are unreliable in a shared CI environment, the
memory usage will be an accurate indicator of space leaks
* Update bench/README
* use origin/master
* default to stack in benchmarks (for CI)
* ignore ghcide-bench and ghcide-preprocessor binaries too
* Review feedbacks
* Add the v0.3.0 tag in bench/hist.yaml
commented out to keep the CI time as tight as possible
* Add .artifactignore file to avoid publishing binaries in azure bench pipeline
* use default stack.yaml
Copy file name to clipboardExpand all lines: README.md
+7-5
Original file line number
Diff line number
Diff line change
@@ -329,15 +329,17 @@ This writes a log file called `.tasty-rerun-log` of the failures, and only runs
329
329
See the [tasty-rerun](https://hackage.haskell.org/package/tasty-rerun-1.1.17/docs/Test-Tasty-Ingredients-Rerun.html) documentation for other options.
330
330
331
331
If you are touching performance sensitive code, take the time to run a differential
332
-
benchmark between HEAD and upstream using the benchHist script. The configuration in
333
-
`bench/hist.yaml` is setup to do this by default assuming upstream is
334
-
`origin/master`. Run the benchmarks with `stack`:
332
+
benchmark between HEAD and master using the benchHist script. This assumes that
333
+
"master" points to the upstream master.
334
+
335
+
Run the benchmarks with `stack`:
335
336
336
337
export STACK_YAML=...
337
338
stack bench
338
339
339
-
It should take around 15 minutes and the results will be stored in the `bench-hist` folder.
340
-
To interpret the results, see the comments in the `bench/hist/Main.hs` module.
340
+
It should take around 15 minutes and the results will be stored in the `bench-hist` folder. To interpret the results, see the comments in the `bench/hist/Main.hs` module.
0 commit comments