-
-
Notifications
You must be signed in to change notification settings - Fork 587
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
Significant slowdown since isort 4.3.5 #848
Comments
@WolfgangFellger Yes I completely agree. I was just about to post the same issue. I'm not sure what's the best way to diagnose the issue, this is just a speed run comparison on a project I'm working on today: Approx 2 seconds with isort 4.3.4:
Approx 30 seconds with isort 4.3.9:
|
Same here: there's a dramatic slowdown as of isort 4.3.5. My current project goes from ~1 to ~30 seconds:
(Full CPU usage in both cases.) I use isort as a continuous interactive tool and a pre-commit check, so this has a major impact on its usability for me. |
@pjdelport It looks like a fix is coming here: #852 |
isort 4.3.4:
isort 4.3.5:
|
I have made another patch which speeds up the finders instead of disabling them: #856. |
I've packaged up @Tenzer's improvement in the latest 4.3.10 release. Thank you! ~Timothy |
Having just tried out the 4.3.10 release I can't see the performance improvements I saw when making the patches. I'll have to dig into why that is, as I can see my code changes are part of the release. |
Going from 4.3.10 to 4.3.16 resolved this for me. |
isort 4.3.5 is a factor of twenty slower for me than 4.3.4 (a run now takes 30s instead of 1.5s, CPU is at 100%). isort 4.3.7 still exhibits the same problem.
Is anybody else seeing that? What diagnostics can I run? Python version is 3.6.8, if that matters.
The text was updated successfully, but these errors were encountered: