mirror of
https://github.com/haskell/ghcide.git
synced 2024-11-29 14:35:24 +03:00
bd51ad0a63
* [bench-hist] save messages to log file And fix the commitid rule to always rerun the git query * Do not build benchHist by default Hopefully avoiding the additional dependencies for charts * Simplify with FileStdout * Add a flag for bench-hist Could benchHist be a benchmark instead of an executable, removing the need for this flag? Almost. `stack bench` fails because `benchHist` cannot find `ghcide-bench` in the path. It seems like a bad idea to have a benchmark that fails out of the box * Turn benchHist into a benchmark and ghcide-bench into an exe This works out nicely because: 1. benchHist already runs ghcide-bench, 2. benchHist has additional deps, but ghcide-bench does not. (benchmark deps don't get built by default) 3. This is the only way I've found to get ghcide-bench in the PATH for benchHist * Remove redundant dep on applicative-combinators * Bump versions in stack-ghc-lib.yaml * update lower bounds for extra in benchHist executable * Update README guideline on benchmarks * [benchHist] Fix the commitid rule to always rerun the git query * fix caps
43 lines
979 B
YAML
43 lines
979 B
YAML
# The number of samples to run per experiment.
|
|
# At least 100 is recommended in order to observe space leaks
|
|
samples: 100
|
|
|
|
# Path to the ghcide-bench binary to use for experiments
|
|
ghcideBench: ghcide-bench
|
|
|
|
# Output folder for the experiments
|
|
outputFolder: bench-hist
|
|
|
|
# The set of experiments to execute
|
|
experiments:
|
|
- hover
|
|
- edit
|
|
- getDefinition
|
|
- "hover after edit"
|
|
- "completions after edit"
|
|
- "code actions"
|
|
- "code actions after edit"
|
|
- "documentSymbols after edit"
|
|
|
|
# An ordered list of versions to analyze
|
|
versions:
|
|
# A version can be defined briefly:
|
|
# - <tag>
|
|
# - <branch>
|
|
# - <commit hash>
|
|
|
|
# Or in extended form, where all the fields are optional:
|
|
# - <name>:
|
|
# git: <tag/branch/commithash>
|
|
# include: true # whether to include in comparison graphs
|
|
# parent: <tag/branch/commithash> # version to compare with in .diff graphs
|
|
|
|
|
|
# - v0.0.5
|
|
# - v0.0.6
|
|
# - v0.1.0
|
|
# - v0.2.0
|
|
- upstream: upstream/master
|
|
- HEAD
|
|
|