-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: refactor LeftCancelMonoid and friends #6011
Conversation
!bench |
Here are the benchmark results for commit ed98890.Found no runs to compare against. |
!bench |
Here are the benchmark results for commit ed98890.Found no runs to compare against. |
My understanding is that this change shaves another 5% of |
!bench |
Here are the benchmark results for commit ed98890.Found no runs to compare against. |
!bench |
Here are the benchmark results for commit ed98890.Found no runs to compare against. |
If I just keep typing !bench will it eventually give me some red and green print-out? !bench |
!bench |
Here are the benchmark results for commit ed98890. Benchmark Metric Change
==============================================================================================
- build maxrss 10.9%
+ ~Mathlib.Algebra.ContinuedFractions.Computation.CorrectnessTerminating instructions -7.5%
+ ~Mathlib.Algebra.Order.Monoid.NatCast instructions -7.7%
- ~Mathlib.Combinatorics.HalesJewett instructions 32.8%
- ~Mathlib.LinearAlgebra.FreeModule.PID instructions 12.8%
- ~Mathlib.RingTheory.ClassGroup instructions 9.0% |
!bench |
Here are the benchmark results for commit ab17523.Found no runs to compare against. |
!bench |
Here are the benchmark results for commit ab17523.Found no runs to compare against. |
!bench |
Here are the benchmark results for commit ab17523.Found no runs to compare against. |
!bench |
Here are the benchmark results for commit ab17523.Found no runs to compare against. |
!bench |
Here are the benchmark results for commit ab17523.Found no runs to compare against. |
!bench |
Here are the benchmark results for commit ab17523.Found no runs to compare against. |
This is an attempt to merge a commit on master which has already been profiled. |
!bench |
Here are the benchmark results for commit bef7e1a. Benchmark Metric Change
==============================================================================================
- build maxrss 5.6%
+ ~Mathlib.Algebra.ContinuedFractions.Computation.CorrectnessTerminating instructions -7.5%
+ ~Mathlib.Algebra.Order.Monoid.NatCast instructions -7.6%
- ~Mathlib.Combinatorics.HalesJewett instructions 32.7%
- ~Mathlib.RepresentationTheory.GroupCohomology.Resolution instructions 5.1%
- ~Mathlib.RingTheory.ClassGroup instructions 5.7%
- ~Std.Lean.TagAttribute instructions 6.7% |
Not only was this a huge declaration, it also remained unfolded throughout checking the proof, so things like defeq checking were extremely slow (total declaration elaboration time ~1 minute on my machine). Splitting it into a `def` + proofs makes everything much faster. Total build time for this file on my machine went from ~140 seconds to ~80 seconds. I came across this issue while trying to figure out why #6011 appeared to slow down building of `ClassGroup.lean`. Co-authored-by: Anne Baanen <Vierkantor@users.noreply.github.com>
I'm surprised that this PR should consistently have such a bad effect on Hales-Jewett. This deserves some further investigation. |
Not only was this a huge declaration, it also remained unfolded throughout checking the proof, so things like defeq checking were extremely slow (total declaration elaboration time ~1 minute on my machine). Splitting it into a `def` + proofs makes everything much faster. Total build time for this file on my machine went from ~140 seconds to ~80 seconds. I came across this issue while trying to figure out why #6011 appeared to slow down building of `ClassGroup.lean`. Co-authored-by: Anne Baanen <Vierkantor@users.noreply.github.com>
Not only was this a huge declaration, it also remained unfolded throughout checking the proof, so things like defeq checking were extremely slow (total declaration elaboration time ~1 minute on my machine). Splitting it into a `def` + proofs makes everything much faster. Total build time for this file on my machine went from ~140 seconds to ~80 seconds. I came across this issue while trying to figure out why #6011 appeared to slow down building of `ClassGroup.lean`. Co-authored-by: Anne Baanen <Vierkantor@users.noreply.github.com>
!bench |
Here are the benchmark results for commit ac47956. |
!bench |
Here are the benchmark results for commit 3580dd4. |
Things have moved on so much since I opened this PR that these changes no longer have any effect. |
Implementing this Zulip suggestion.