tree: 73ded4dd9ce7c3af45543978dd4839e27cc7eada [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_mul.lean
  20. bv_decide_realworld.lean
  21. compile.sh
  22. const_fold.hs
  23. const_fold.lean
  24. const_fold.lean.args
  25. const_fold.lean.expected.out
  26. const_fold.ml
  27. const_fold.sml
  28. const_fold.swift
  29. cross.yaml
  30. dag_hassorry_issue.lean
  31. dag_hassorry_issue.lean.args
  32. dag_hassorry_issue.lean.expected.out
  33. deriv.hs
  34. deriv.lean
  35. deriv.lean.args
  36. deriv.lean.expected.out
  37. deriv.ml
  38. deriv.sml
  39. deriv.swift
  40. ex-50-50-1.leq
  41. flake.lock
  42. flake.nix
  43. full-stdlib.exec.yaml
  44. ghc-gc.py
  45. ilean_roundtrip.lean
  46. lean-gc.py
  47. liasolver.lean
  48. liasolver.lean.args
  49. liasolver.lean.expected.out
  50. Makefile
  51. mlkit-gc.py
  52. nat_repr.lean
  53. nat_repr.lean.args
  54. nat_repr.lean.expected.out
  55. ocaml-gc.py
  56. parser.lean
  57. perf.py
  58. qsort.hs
  59. qsort.lean
  60. qsort.lean.args
  61. qsort.lean.expected.out
  62. qsort.ml
  63. qsort.sml
  64. qsort.swift
  65. rbmap.hs
  66. rbmap.lean
  67. rbmap.lean.args
  68. rbmap.lean.expected.out
  69. rbmap.ml
  70. rbmap.sml
  71. rbmap.swift
  72. rbmap2.lean
  73. rbmap3.lean
  74. rbmap500k.lean
  75. rbmap_checkpoint.hs
  76. rbmap_checkpoint.lean
  77. rbmap_checkpoint.lean.args
  78. rbmap_checkpoint.lean.expected.out
  79. rbmap_checkpoint.ml
  80. rbmap_checkpoint.sml
  81. rbmap_checkpoint.swift
  82. rbmap_checkpoint2.lean
  83. rbmap_checkpoint2.sml
  84. rbmap_checkpoint_cpp_lean3.cpp
  85. rbmap_checkpoint_cpp_std.cpp
  86. rbmap_cpp_lean3.cpp
  87. rbmap_cpp_std.cpp
  88. rbmap_fbip.lean
  89. rbmap_library.lean
  90. README.md
  91. reduceMatch.lean
  92. report.py
  93. run.sh
  94. server_startup.lean
  95. server_startup.log
  96. speedcenter.exec.velcom.yaml
  97. speedcenter.yaml
  98. states35.lean
  99. test_single.sh
  100. unionfind.lean
  101. unionfind.lean.args
  102. unionfind.lean.expected.out
  103. unionfind_clean.lean
  104. 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.