Skip to content

Mitigate slow kernel discovery (API adoption, placeholder kernels, measurements)  #9628

@DonJayamanne

Description

@DonJayamanne

#5861

Problems

  • Unable to run a cell after opening a notebook for first time after installing VS Code
    • Basically user needs until all Python interpreters have been discovered. This can be very slow depending on a number of factors.
    • The users perception is They cannot run a cell

Tasks/Suggestions:

  • Review (& provide feedback) the new Python API
    • What will it take to implement this
    • Do we need changes in the API
  • Progress indicator for kernels loading/being fetched (would be be of any value?)
  • Add a placeholder lazy kernel for Python? (see corresponding issue with usecases for Lazy kernels)
  • Add active interpreter as a controller (while discovering other interpreters)
  • Add telemetry (if we don't already have this) to determine how quickly we return controllers
  • Add telemetry (if we don't already have this) to determine how quickly we get interpreters from Python extension

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssue identified by VS Code Team member as probable bugnotebook-getting-started

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions