-
Notifications
You must be signed in to change notification settings - Fork 15
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
Extreme runtime increase #172
Comments
|
Can we add timing info to the mathport logs? For example, the time taken for binport and synport on each file. Also, it doesn't seem like the mathlib commit is available from the logs - I can only find the commits for lean3, lean4, and mathlib4. |
I've added the mathlib commit info to both the log as well as the predata tarball. I'm not sure if the timing is helpful. But at least we can now try this out locally: ./download-predata.sh predata-nightly-2022-08-26
rm -rf Outputs
./build/bin/mathport --make config.json Mathbin::data.analysis.filter |
Hooked up a profiler to
I guess we accidentally (?) made some function computable in mathlib and now we're running the compiler on everything. |
I think we should probably force_noncomputable everything in mathbin. The terms are not appropriate for evaluation by lean 4 and it's a bit dangerous to assume they are. (If that's too heavy a hammer, we could put a small timeout on the compiler and give up otherwise.) |
Hmm, now it hangs at ζ-reduction in
|
Oh, is this with leanprover/lean4#1512? That would at least explain |
No, without. Maybe 1512 fixes this issue. |
The latest timeouts don't seem to be caused by a simple infinite loop. It's just that many files now take a lot longer than they used to. For example here is what's running right now:
data.analysis.filter
has been running for 75 minutes and is not finished yet, but I think it will finish at some point. To compare,topology.local_homeomorph
was running for 20 minutes but finished then.This seems to be due to a mathlib change between August 23 (successful build) and August 25 (first timeout). As far as I can tell, nothing changed on the mathport end.
The text was updated successfully, but these errors were encountered: