tree: 7a05807c8cffafe77aafe658288f6b54a933f9cf [search]
  1. inundation/
  2. mergeSort/
  3. .gitignore
  4. accumulate_profile.py
  5. arith_eval.ml
  6. binarytrees.ghc-6.hs
  7. binarytrees.lean
  8. binarytrees.lean.args
  9. binarytrees.lean.expected.out
  10. binarytrees.ocaml-2.ml
  11. binarytrees.st.hs
  12. binarytrees.st.lean
  13. binarytrees.st.mlton-2.sml
  14. binarytrees.st.sml
  15. binarytrees.st.swift
  16. binarytrees.swift
  17. binarytrees5.ml
  18. binarytrees5_multicore.ml
  19. bv_decide_mod.lean
  20. bv_decide_mul.lean
  21. bv_decide_realworld.lean
  22. compile.sh
  23. const_fold.hs
  24. const_fold.lean
  25. const_fold.lean.args
  26. const_fold.lean.expected.out
  27. const_fold.ml
  28. const_fold.sml
  29. const_fold.swift
  30. cross.yaml
  31. dag_hassorry_issue.lean
  32. dag_hassorry_issue.lean.args
  33. dag_hassorry_issue.lean.expected.out
  34. deriv.hs
  35. deriv.lean
  36. deriv.lean.args
  37. deriv.lean.expected.out
  38. deriv.ml
  39. deriv.sml
  40. deriv.swift
  41. ex-50-50-1.leq
  42. flake.lock
  43. flake.nix
  44. full-stdlib.exec.yaml
  45. ghc-gc.py
  46. ilean_roundtrip.lean
  47. lean-gc.py
  48. liasolver.lean
  49. liasolver.lean.args
  50. liasolver.lean.expected.out
  51. Makefile
  52. mlkit-gc.py
  53. nat_repr.lean
  54. nat_repr.lean.args
  55. nat_repr.lean.expected.out
  56. ocaml-gc.py
  57. parser.lean
  58. perf.py
  59. qsort.hs
  60. qsort.lean
  61. qsort.lean.args
  62. qsort.lean.expected.out
  63. qsort.ml
  64. qsort.sml
  65. qsort.swift
  66. rbmap.hs
  67. rbmap.lean
  68. rbmap.lean.args
  69. rbmap.lean.expected.out
  70. rbmap.ml
  71. rbmap.sml
  72. rbmap.swift
  73. rbmap2.lean
  74. rbmap3.lean
  75. rbmap500k.lean
  76. rbmap_checkpoint.hs
  77. rbmap_checkpoint.lean
  78. rbmap_checkpoint.lean.args
  79. rbmap_checkpoint.lean.expected.out
  80. rbmap_checkpoint.ml
  81. rbmap_checkpoint.sml
  82. rbmap_checkpoint.swift
  83. rbmap_checkpoint2.lean
  84. rbmap_checkpoint2.sml
  85. rbmap_checkpoint_cpp_lean3.cpp
  86. rbmap_checkpoint_cpp_std.cpp
  87. rbmap_cpp_lean3.cpp
  88. rbmap_cpp_std.cpp
  89. rbmap_fbip.lean
  90. rbmap_library.lean
  91. README.md
  92. reduceMatch.lean
  93. report.py
  94. run.sh
  95. server_startup.lean
  96. server_startup.log
  97. speedcenter.exec.velcom.yaml
  98. speedcenter.yaml
  99. states35.lean
  100. test_single.sh
  101. unionfind.lean
  102. unionfind.lean.args
  103. unionfind.lean.expected.out
  104. unionfind_clean.lean
  105. workspaceSymbols.lean
tests/bench/README.md

Lean Benchmark Suites

This folder contains multiple small Lean programs for benchmarking used by two separate benchmark suites based on the temci benchmarking tool:

  • The light-weight “Speedcenter” suite benchmarks the current build of Lean. It can be used for quick comparisons on the cmdline and powers the Lean Speedcenter website.
  • The heavy-weight “Cross” suite benchmarks multiple Lean configurations and other functional compilers against each other and generates CSV and HTML reports from that. It was created for the paper “Counting Immutable Beans - Reference Counting Optimized for Purely Functional Programming” (IFL19).

Speedcenter Suite

Requirements:

  • A local Lean build in ../../build/release. Build at least the bin target.
  • temci. Using Nix, open a nix-shell in the project root directory to add a compatible version to your PATH. Alternatively, try pip3 install git+https://github.com/parttimenerd/temci.git.

To execute the suite and save the results in base.yaml, run (in this folder)

temci exec --config speedcenter.yaml --out base.yaml

Other interesting exec flags:

  • use --runs N to modify the default number of 10 runs per benchmark
  • use --included_blocks fast to excluded slow benchmarks like the stdlib benchmark. You can replace fast with any benchmark name or label in speedcenter.exec.yaml.

If you have multiple saved result files, you can compare them with

temci report --config speedcenter.yaml report1.yaml report2.yaml ...

Cross Suite

We recommend using Nix for building/obtaining all Lean variants and used compilers in a reproducible way. After installing Nix, running the benchmarks is as easy as

nix develop
make

This will record 50 runs for each benchmark configuration (this can be changed with runs in cross.yaml), generate results in report_lean.csv and report_cross.csv, and print them to stdout in a tabulated format. It will also generate HTML reports in report/ comparing the time-based benchmarks.

In order to reduce noise in the benchmarking data, you may instead want to try calling make inside a temci shell:

temci short shell --sudo --preset usable --cpuset_active make

Using root powers, this will temporarily configure your machine similarly to the LLVM benchmarking recommendations and move all your other processes to a single CPU core.