1. 26 Jan, 2019 1 commit
  2. 16 Jan, 2019 3 commits
  3. 15 Jan, 2019 2 commits
  4. 13 Jan, 2019 1 commit
  5. 08 Jan, 2019 1 commit
    • Sebastian Graf's avatar
      Stabilise benchmarks wrt. GC · 8632268a
      Sebastian Graf authored
      This is due to #15999, a follow-up on #5793 and #15357 and changes all
      benchmarks, some of them (i.e. `wheel-sieve1`, `awards`) rather drastically.
      The general plan is outlined in #15999: Identify GC-sensitive benchmarks by
      looking at how productivity rates change over different nursery sizes and
      iterate `main` of these benchmarks often enough for the non-monotony and
      discontinuities to go away.
      I was paying attention that the benchmarked logic is actually run $n times more
      often, rather than just benchmarking IO operations printing the result of CAFs.
      When I found benchmarks with insignificant runtime (#15357), I made sure that
      parameters/input files were adjusted so that runtime of the different modes
      fall within the ranges proposed in
      - fast: 0.1-0.2s
      - norm: 1-2s
      - slow: 5-10s
      This is what I did:
      - Stabilise bernoulli
      - Stabilise digits-of-e1
      - Stabilise digits-of-e2
      - Stabilise gen_regexp
      - Adjust runn...
  6. 01 Jan, 2019 5 commits
  7. 30 Dec, 2018 1 commit
  8. 29 Dec, 2018 1 commit
  9. 26 Dec, 2018 1 commit
    • Sebastian Graf's avatar
      Compare results of compress by hashing · 042cf0be
      Sebastian Graf authored
      We don't want the result in the repo as it's a sizeable binary file that
      doesn't compress well.
      Storing the output file in the repository becomes infeasible for large
      inputs. There are two possible remedies:
      1. Generate the result files during `make boot` (Phab:D5426). We
         discovered some drawbacks (like missing dependency files to build
         `compress` during boot) to this approach which make it infeasible.
      2. Shrink the output files, for example by hashing the string that we would
         normally output and compare that instead.
      This patch implements the second alternative. This somewhat distorts the
      runtime profile, so we might want to consider doing hashing within the
      benchmark runner in the future.
      Test Plan: make boot
      Reviewers: AndreasK, nomeata, O26 nofib, osa1
      Reviewed By: AndreasK, osa1
      Subscribers: osa1
      Differential Revision: https://phabricator.haskell.org/D5469
  10. 22 Dec, 2018 1 commit
  11. 21 Dec, 2018 1 commit
    • Sebastian Graf's avatar
      Fix parsing of maximum residency in runstdtest · f3521319
      Sebastian Graf authored
      `runstdtest` switched from `-S` to `-s` output a while ago.
      That broke parsing of maximum and average residency numbers.
      This commit makes sure that at least maximum residency is parsed
      correctly from `-s` output, while leaving the logic for `-S` output.
      Reviewers: simonmar, bgamari, simonpj, osa1, AndreasK, O26 nofib
      Reviewed By: bgamari
      GHC Trac Issues: #16003
      Differential Revision: https://phabricator.haskell.org/D5418
  12. 22 Nov, 2018 2 commits
  13. 20 Nov, 2018 1 commit
  14. 14 Nov, 2018 1 commit
    • Andreas Klebinger's avatar
      Adjust normal runtimes for nofib along with related changes · 08cc9b6b
      Andreas Klebinger authored
      Runtime for nofib benchmarks was all over the place.
      This patch adjusts runtime for most benchmarks such
      that it falls into the 0.2-2s range.
      This means that:
      * A default run will take longer
      * Time spent will be better distributed among benchmarks.
      * More benchmarks have runtimes long enough to be used
        for runtime analysis.
      Some more changes were done which go hand in hand
      with changing runtimes.
      * Some benchmarks now create their input files during boot.
      * Moved input files for anna in their own directory.
      * Remove printing of output for some of the floating
        point heavy benchmarks.
      * Added a comment about desired runtimes to README.
      * Made grep actually benchmark something.
      * Throw cachgrind out of the default benchmarks.
        The nondeterministic behaviour has been an issue for a
        while and it doesn't seem like an essential benchmark.
      Test Plan: run nofib in modes slow/normal/fast
      Reviewers: O26 nofib, alpmestan
      Reviewed By: alpmestan
      Subscribers: sgraf, alpmestan
      Differential Revision: https://phabricator.haskell.org/D4989
  15. 27 Aug, 2018 1 commit
  16. 22 Aug, 2018 1 commit
  17. 20 Jun, 2018 1 commit
  18. 16 Jun, 2018 5 commits
  19. 04 May, 2018 1 commit
  20. 08 Feb, 2018 1 commit
  21. 17 Jan, 2018 1 commit
  22. 28 Dec, 2017 1 commit
  23. 23 Oct, 2017 2 commits
  24. 22 Oct, 2017 2 commits
  25. 14 Sep, 2017 1 commit
  26. 23 Aug, 2017 1 commit