-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
mypy_primer is very slow #6481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its main 8000 tainers 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
Comments
So what can we do to bring it back to run under 10 minutes again? Everything above that, and it just becomes a hindrance more than a help. Can we segment it? Or only run for projects that are potentially affected by the changes? |
Options:
Not sure how you would determine projects potentially affected by changes (note we don't run primer on changes to third party stubs anyway, since modular typeshed) |
One idea to determine potentially affected projects: Cache the modules imported by a project (basically do a Do we have any performance data what the bottlenecks are? What would make sense to cache? |
Given that mypy 0.920 is like 2x faster for mypy_primer like usage, I was surprised to not see the gain. It looks like I broke the logic that made typeshed use wheels from PyPI, so we have been running pure Python mypy for the last couple weeks :-) Anyway, all fixed, and I expect that should resolve this. |
Within the last week, mypy_primer has become very slow. Where previously, it ran in about 10 minutes, it now needs over 45. What could be the cause for that?
The text was updated successfully, but these errors were encountered: