-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add --threads argument to pyright cli #12688
Conversation
Does this actually speed things up much?
So for our purposes, this argument might slow things down? |
About a second locally (17.45s vs 18.81s average) running Even if within the same GitHub action, there's 1-2s variance between jobs, I think we can revert, including the non-CI part. I'm not gonna fight for a ~1s improvement (which is whithin some run to run variance) on a 16 logical core CPU when it might make others' run slower ^^". |
Without having looked into it at all: it might well be the kind of thing where a huge codebase with very large packages in it would get a speedup from |
We already get a ton of parallelism from running so many different GH Actions; I think it makes sense that we don't get much gain from further parallelizing within each action. It might help more when run locally but the speedup @Avasam posted doesn't seem that compelling. |
This reverts commit f0e16b8. See conversation in python#12688: for this repo, it seems like the argument actually makes pyright run slower, rather than faster.
I opened #12690 to revert |
Available since https://github.com/microsoft/pyright/releases/tag/1.1.371 , crash fixed in https://github.com/microsoft/pyright/releases/tag/1.1.377 (microsoft/pyright#8775)