startup time approximately 2 seconds

[gurkanctn]

• Extension Name: python
• Extension Version: 0.9.1
• OS Version: Windows_NT x64 10.0.16299
• VSCode version: 1.19.3

We have written the needed data into your clipboard. Please paste:

{
	"activationTimes": {
		"startup": false,
		"codeLoadingTime": 1545,
		"activateCallTime": 162,
		"activateResolvedTime": 44,
		"activationEvent": "onLanguage:python"
	}
}

[DonJayamanne]

@gurkanctn
Currently when the extension loads, it tries to locate interpreters on your current system (one time operation), this list is then used to allow users to change the interpreter for the workspace.
I believe this is where the majority of the delay is.

Would you be kind enough to explain how this currently effects your current workflow.
How did you experience this delay when using the extension before looking at the activation times.

[DonJayamanne]

Added awaiting 2-PR as we can make some minor improvements to the performance.

[MikhailArkhipov]

So it is codeLoadingTime that takes the most.

[DonJayamanne]

Closing this issue as we've improved the performance to bring it down to under 500ms.
Changes should be available in the current release of the extension.

How to test:

• Open a workspace with python files
• Open a python file (to activate the python extension)
• Go into the command palette and select Developer: Startup Performance
• A table will be rendered in the console window

Closed via #953 and #931. Further performance improvements will be tracked under #951

[gurkanctn]

@DonJayamanne , thanks a lot for the improvement.

At the table you mentioned, my duration adds up to 80. But I don't know the unit of it. I didn't measure myself but it definitely is not 80 msecs. Still, I felt an improvement at startup with the February version (that I upgraded right now).

[DonJayamanne]

The values in the table are provided by vscode, not the extension.