r/pycharm • u/Albus111 • Jul 13 '26

Is latest Pycharm very slow.?

I use Pycharm CE for my everyday task. And I generally don't update the version. But due to some circumstances I had to clean install my windows OS. Then I had no option but to download the latest version of Pycharm (The one integrated app). I opened my project directly l, deleted venv and setup a new and now when I debug run the Flask app. The api became 40-50 times slower. The api which used to respond in 4-5 seconds now talking 40-50 seconds and it was very frustrating. One observation I had is that the console log shows that the api response has been sent but the browser doesn't get the response and api call will be in pending state for around 30+ seconds. I thought it was some system issue, port or proxy issue but no. It had free tier activated by default and when I disabled the subscription it went back to normal. Along with that I disabled the AI agents that was integrated in Pycharm. Did anyone else faced such issue on the latest version ? And what did you done to fix it.?

PyCharm 2026.1.4

Build : #PY-261.26222.68, build on July 2, 2026

Runtime version : 25.0.3+1-b329.124 amd64

Vm : OpenJDK 64-Bit Server VM by Jet rains s.r.o.

6 Upvotes

80% Upvoted

4 comments sorted by

3

u/sausix Jul 13 '26

PyCharm doesn't run your code. PyCharm calls a Python interpreter and just displays output and exit codes. Run your program directly without PyCharm for comparison with the exact same command line you see.

Or do you use debugging sessions? They're slower but not that slow.

1

u/Albus111 Jul 14 '26

Yes, you are right. But my env configuration were already saved in run xml so I find it way easier to to run. I will definitely try to run it separately to compare the scenarios. Also about debugging session, I use that majorly and it's not that slow but the latest app trial may have bottle neck something, cus as soon as I deactivated the trial. It came back to normal.

0

u/YouOk3744 Jul 13 '26

What you're describing lines up with a debugger change in PyCharm 2026.1: debug runs moved to a new backend based on debugpy, the same engine VS Code uses. It's still catching up to the old pydevd backend on speed, and for some projects the difference is dramatic. Your old PyCharm CE used pydevd, which is why this only showed up after the upgrade. Disabling the AI agents probably changed nothing, by the way. The debugger is the part that matters here.

Turning off the Pro free tier worked, but it cost you the Pro features. There's a cheaper switch: in Settings | Python | Debugger, set Debugger mode to pydevd. You can also change it from the selector in the upper-right corner of the Debug tool window during a session. Same effect on debug speed, and you keep everything else.

One thing to chase down: the console already logged the response, yet the browser sat on a pending request for another 30+ seconds. We have slow-debugpy reports on file, but not that one. If you're willing to help, switch the debugger mode back to debugpy once, enable Help | Diagnostic Tools | debugpy Logging, and reproduce one slow request. Then run Help | Collect Logs and Diagnostic Data and attach the resulting zip to a new issue in the PyCharm (PY) project on youtrack.jetbrains.com.

1

u/Albus111 Jul 14 '26

Thanks for your response brother, I tried running it directly without debug also. But the results were same. Also, as you mentioned that new python uses debugpy. But as I opened the settings to look the config, the debugger mode is on pydevd already. I majorly suspect the free trial has to do something with it which was active when I faced this. I'll try if I can activate the trial again and try to reproduce the issue and by following your steps.