My rant on Indexing again
I've been a PyCharm user since it's first released. For personal projects within a relatively small PYTHONPATH it works great.
Now I work in a company with 15+ years of Python code base. Hundreds of packages in PYTHONPATH on a shared network path.
99% of those packages NEVER change. Also, I'm working on multiple projects at a time and every time I open PyCharm it starts indexing THE SAME hundreds of packages AGAIN.
There are dozens of complaints on indexing but JetBrains for some reason is completely ignorant about this problem.
We're not asking to make it faster, or make the problem magically disappear, just PLEASE give us the ability to control this process:
- Exclude paths from indexing. Super important! We still need some paths to be in PYTHONPATH, so they can't be removed, but they NEVER change, there is absolutely reason to reindex them every single time.
- Disable the indexing whatsoever on demand.
- Allow the indexing to run once and DO NOT re-index on restart unless explicitly asked.
- Prioritize other IDE actions over indexing. While PyCharm is indexing the IDE is pretty much useless.
Please make PyCharm great again by giving us control over the indexing!
请先登录再写评论。
Thank you, Ervis. I understand this is not supported. I suppose I will submit a feature request to prevent indexing of folders excluded mid-indexing.
Struggling with the same issue basically. PyCharm gets hammered by indexing eating 700% cpu constantly like 95% of the time. Please make a manual mode for reindexing. Alternatively make a configurable cap on resources usage that can be used by indexing. I'm really holding myself from switching to VS Code.
Alexander Work63 please create a new performance issue on YouTrack so we can investigate this case further.
If possible share a minimal reproducible sample project that demonstrates this behavior. If sharing the project is not possible, please provide a short screen recording or a few screenshots showing the IDE, the project structure, and the steps leading to the issue.
Additionally, please capture a CPU snapshot (Help | Diagnostic Tools | Capture CPU Snapshot) after reproducing the problem.
IDE logs from Help | Collect Logs and Diagnostic Data would also be very helpful.
This information will help us investigate the behavior more effectively.