You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Spike: Investigate using webworker for Python discovery #21755
Resolver & locator part are expensive, watcher can be outside. The issue right now is watcher is part of the locator, locator gives out existing environment locations and watcher returns whether there's an new env in those locations.
Activity
Frnchy1 commentedon Aug 4, 2023
karrtikr commentedon Sep 14, 2023
Spike
Discovery = locator + watcher + resolver
vscodemodule is not available to use in worker threads, so we have to refactor them out. APIs we currently use:workspace.workspaceFoldersandworkspace.onDidChangeWorkspaceFoldersworkspace.createFileSystemWatcher,EventEmitter,RelativePatternUriitselfResolver & locator part are expensive, watcher can be outside. The issue right now is watcher is part of the locator, locator gives out existing environment locations and watcher returns whether there's an new env in those locations.
karrtikr commentedon Sep 21, 2023
Spawning conda or "REG" binary (windows registry) can block the main thread for a few seconds:

karrtikr commentedon Sep 21, 2023
Perf analysis of where time is spent on extension load, and how discovery impacts it:
Fix bugs related to discovery blocking other features (#22041)
Fix bugs related to discovery blocking other features (microsoft#22041)
karrtikr commentedon Oct 3, 2023
Spike results: #22146 (comment)