Making Pylint faster 3 #545
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes just one change, namely caching the result of the function
lookup
. The impact of this change seems to be proportional to the size of the project. Here are the results of timing before and after againstzulip/zerver
(a large directory belonging to the Zulip chat app) and againstpycodestyle.py
.zulip/zerver
Before
After
pycodestyle.py
Before
After
(By the way, you might look at the numbers here and notice that they are substantially less than the numbers presented in my previous PRs. This is because those times were recorded with a profiler enabled. It seems obvious in hindsight that running a program with a profiler enabled would cause it to run slower, even substantially slower, but live and learn I guess. In any case, these are real times.)