Loading the virtual environment is too slow

[jalenzz]

2025-08-19 07:36:53.413 [info] Starting Python Locator xxx server
2025-08-19 07:36:53.413 [info] Using conda from persistent state: /opt/conda/condabin/conda
2025-08-19 07:37:46.494 [info] Resolved Python Environment /home/xx/xxx/.venv/bin/python
2025-08-19 07:37:46.712 [info] Discovered env: /home/xx/xxx/.venv/bin/python
2025-08-19 07:37:46.860 [info] Locator GlobalVirtualEnvs took 561ns
2025-08-19 07:37:46.915 [info] Locator Locators took 551ns
2025-08-19 07:37:46.920 [info] Locator Path took 681ns
2025-08-19 07:37:46.928 [info] Locator Workspaces took 4.089947ms
2025-08-19 07:37:46.929 [info] Telemetry:  {"event":"RefreshPerformance","data":{"refreshPerformance":{"total":4,"breakdown":{"GlobalVirtualEnvs":0,"Locators":0,"Path":0,"Workspaces":4},"locators":{}}}}
2025-08-19 07:37:46.952 [info] Found venv environment: xxx (3.12.11)
2025-08-19 07:37:46.959 [info] Discovered env: /home/xxx/xxx/.venv/bin/python
2025-08-19 07:37:47.024 [info] Discovered manager: (Conda) /opt/conda/bin/conda
2025-08-19 07:37:47.025 [info] Discovered env: /opt/conda/bin/python
2025-08-19 07:37:47.025 [info] Discovered env: /home/xxx/.conda/envs/xxx
2025-08-19 07:37:47.025 [info] Discovered env: /home/xxx/.conda/envs/xxx
2025-08-19 07:37:47.025 [info] Discovered env: /home/xxx/.conda/envs/xxx
2025-08-19 07:37:47.025 [info] Discovered env: /home/xxx/.conda/envs/xxx
2025-08-19 07:37:47.025 [info] Discovered env: /home/xxx/.conda/envs/xxx
2025-08-19 07:37:47.025 [info] Discovered env: /home/xxx/.conda/envs/xxx
2025-08-19 07:37:47.025 [info] Discovered env: /home/xxx/.conda/envs/xxx
2025-08-19 07:37:47.026 [info] Discovered env: /home/xxx/.conda/envs/xxx
2025-08-19 07:37:47.026 [info] Discovered env: /home/xxx/.conda/envs/xxx
2025-08-19 07:37:47.026 [info] Discovered env: /usr/bin/python3
2025-08-19 07:37:47.026 [info] Discovered env: /bin/python3

It took a full minute just from Using conda from persistent state to Resolved Python Environment. Every time I reopen VSCode, I have to wait a whole minute for this virtual environment to load, that's painfully slow.

[eleanorjboyd]

Thank you for the bug report, yes that is very slow. Could you try running Python: Run Python Environment Tool (PET) in Terminal... from the command palette and select "find". Let me know how long this takes and if it is longer or shorter than what you experienced with the UI. From there I can track down which part we need to focus on for finding the slowdown.

[jalenzz]

@eleanorjboyd Python: Run Python Environment Tool show Completed in 119ms

But is this timing really effective? I tried run this command as soon as VSCode opens, but the command just hangs until the extensions finish loading and the virtual environment initializes. It only works properly after the virtual environment is fully set up.

[jalenzz]

I opened VS Code and immediately ran "Running PET in terminal," but the logs show it didn't respond to the command until 02:10:39 despite being initiated at 02:09:46. It takes nearly a minute to respond. How can I check what happened during that minute?

2025-08-22 02:09:46.718 [info] Starting Python Locator /home/xxx/.vscode-server/extensions/ms-python.vscode-python-envs-1.2.0/python-env-tools/bin/pet server
2025-08-22 02:09:46.718 [info] Using conda from persistent state: /opt/conda/condabin/conda
2025-08-22 02:09:46.718 [info] Extension for manager ms-python.python:venv is not active: Activating...
2025-08-22 02:09:46.718 [info] Extension for manager ms-python.python:venv is now active.
2025-08-22 02:10:39.788 [info] Discovered env: /home/xxx/xxx/.venv/bin/python
2025-08-22 02:10:39.829 [info] Running PET in terminal: /home/xxx/.vscode-server/extensions/ms-python.vscode-python-envs-1.2.0/python-env-tools/bin/pet
2025-08-22 02:10:40.312 [info] Locator GlobalVirtualEnvs took 271ns
2025-08-22 02:10:40.792 [info] Locator Locators took 541ns
2025-08-22 02:10:40.834 [info] Locator Path took 421ns
2025-08-22 02:10:40.842 [info] Locator Workspaces took 3.418642ms

If you need more information, please let me know. BTW, are you experiencing this issue yourself, or is it just me so far?

[eleanorjboyd]

I haven't noticed an issue but have a different number and makeup of environments. Currently the Python extension uses this PET executable to find environments (as well as the environments extension). Do you see lag with just the Python extension?

@karthiknadig and @DonJayamanne for thoughts on time taken for PET

[DonJayamanne]

@eleanorjboyd can we get some instructions for @jalenzz to get the trace logs, perhaps the trace logs will have more information on what's going on.

Looking at perf logs could also help figure out what's going on
@jalenzz pleaser can yoy capture ands share the perf logs as described here https://github.com/microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions

opened VS Code and immediately ran "Running PET in terminal," but the logs show it didn't respond to the command until

Lets not worry about how long PET takes to run from the command palette as soon as you load VS Code.
Running a Command as soon as you load VS Code will be as fast as the extension activates.
This is because VS Code will not run the command until the relevant extension completes activation.

@eleanorjboyd
The following logs indicate that something else is running slow or taking time
Hopefully trace/verbose logging with the perf logs will shed more light here.

2025-08-22 02:09:46.718 [info] Extension for manager ms-python.python:venv is now active.
2025-08-22 02:10:39.788 [info] Discovered env: /home/xxx/xxx/.venv/bin/python
2025-08-22 02:10:39.829 [info]

[DonJayamanne]

@jalenzz
Please can you run the following in your terminal and let me know how long it takes
I doubt this will shed much light as the logs indicate that things are a little slow even before this.

/home/xxx/.vscode-server/extensions/ms-python.vscode-python-envs-1.2.0/python-env-tools/bin/pet resolve /home/xx/xxx/.venv/bin/python

[jalenzz]

@DonJayamanne about 20ms to run

/home/xxx/.vscode-server/extensions/ms-python.vscode-python-envs-1.2.0/python-env-tools/bin/pet resolve /home/xx/xxx/.venv/bin/python

[jalenzz]

CPU-20250823T023204.045Z.cpuprofile.txt

[jalenzz]

@DonJayamanne @eleanorjboyd Thanks for your help. I just tried to troubleshoot whether other extensions were causing the lag. It seems to be GitHub Copilot. After disabling GitHub Copilot, the whole process became much faster. When I re-enabled GitHub Copilot, the lag returned, and in the Running Extensions, GitHub Copilot showed an activation time of over 30s.

Should I go to them for help?

[github-actions]

Hey @eleanorjboyd, this issue might need further attention.

@jalenzz, you can help us out by closing this issue if the problem no longer exists, or adding more information.