-
Notifications
You must be signed in to change notification settings - Fork 12
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
Combinatorial explosion #259
Comments
I just tried test8 and it took 814 seconds while also using quite a lot of memory (maybe 6GB). |
Thank you! I'm curious to see if we can improve it 😄 |
In case it's useful for diagnosis, I'll repeat the observation from #250 that times can vary drastically depending on how one composes. |
Hi @guillaumebrunerie, I've re-tested this example now and there is still an explosion, but it is generally much faster now. Here's the results on my laptop:
Here is your code updated to work on the latest version of
|
This is today’s example of combinatorial explosion (the same issue is present in cubicaltt), which might be why we didn’t manage to compute pi_4(S^3) yet.
Each test has twice as many comp’s as the previous one, but takes about 10 times longer to type check.
For instance test7 is basically the composition of 127 copies of the identity function, so it shouldn’t take as long as 102 second to apply it.
The text was updated successfully, but these errors were encountered: