⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@chenson2018
Copy link
Collaborator

@chenson2018 chenson2018 commented Jan 23, 2026

Please do not review yet, this PR is for initial benchmarking of inlining grind annotations.

@chenson2018
Copy link
Collaborator Author

!radar

@leanprover-radar
Copy link

leanprover-radar commented Jan 23, 2026

Benchmark results for 4bde46f against 02e2a23 are in! @chenson2018

Warning

These warnings may indicate that the benchmark results are not directly comparable, for example due to changes in the runner configuration or hardware.

  • Bench repo commit hashes for run main differ between commits.

Large changes (1✅)

  • build/module/Cslib.Languages.LambdaCalculus.LocallyNameless.Fsub.Typing//instructions: -12.7G (-7.3%)

Medium changes (1✅)

  • build/module/Cslib.Languages.LambdaCalculus.LocallyNameless.Fsub.Safety//instructions: -22.5G (-33.6%)

Small changes (1🟥)

  • 🟥 build/module/Cslib.Languages.LambdaCalculus.LocallyNameless.Fsub.WellFormed//instructions: +12.7G (+11.3%)

@chenson2018
Copy link
Collaborator Author

!radar

@leanprover-radar
Copy link

leanprover-radar commented Jan 23, 2026

Benchmark results for b6c5720 against 02e2a23 are in! @chenson2018

Warning

These warnings may indicate that the benchmark results are not directly comparable, for example due to changes in the runner configuration or hardware.

  • Bench repo commit hashes for run main differ between commits.

Large changes (1✅)

  • build/module/Cslib.Languages.LambdaCalculus.LocallyNameless.Fsub.Typing//instructions: -11.7G (-6.7%)

Medium changes (1✅)

  • build/module/Cslib.Languages.LambdaCalculus.LocallyNameless.Fsub.Safety//instructions: -22.5G (-33.6%)

@chenson2018
Copy link
Collaborator Author

!radar

@leanprover-radar
Copy link

leanprover-radar commented Jan 23, 2026

Benchmark results for dee05e5 against 02e2a23 are in! @chenson2018

Warning

These warnings may indicate that the benchmark results are not directly comparable, for example due to changes in the runner configuration or hardware.

  • Bench repo commit hashes for run main differ between commits.

Large changes (1✅)

  • build/module/Cslib.Languages.LambdaCalculus.LocallyNameless.Fsub.Typing//instructions: -13.3G (-7.6%)

Medium changes (1✅)

  • build/module/Cslib.Languages.LambdaCalculus.LocallyNameless.Fsub.Safety//instructions: -22.6G (-33.6%)

Small changes (1✅)

  • build/module/Cslib.Languages.LambdaCalculus.LocallyNameless.Fsub.Subtype//instructions: -13.9G (-12.7%)

@chenson2018
Copy link
Collaborator Author

I think this at least identifies some of the problem areas. I'd still like to see if a pattern can guard against these instead of having to always specify them by hand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants