Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notebooks - Connecting to kernel taking incredibly long time #8037

Closed
claudiaregio opened this issue Oct 26, 2021 · 4 comments
Closed

Notebooks - Connecting to kernel taking incredibly long time #8037

claudiaregio opened this issue Oct 26, 2021 · 4 comments
Labels
bug Issue identified by VS Code Team member as probable bug perf Performance issues

Comments

@claudiaregio
Copy link
Contributor

Environment data

  • VS Code version: 1.62.0-insider
  • Jupyter Extension version (available under the Extensions sidebar): v2021.10.1001380329

When running my notebook, I can consistently reproduce the notebook taking 30s-60s just to connect to the kernel before it even starts running cells

@claudiaregio claudiaregio added bug Issue identified by VS Code Team member as probable bug perf Performance issues nb-golden labels Oct 26, 2021
@DonJayamanne
Copy link
Contributor

DonJayamanne commented Oct 26, 2021

isn't this a duplicate of ?
#7849
#7069

Its possible its a dup of #7134 (where its slow even in Jupyter lab/notebook, outside VSCode)

@claudiaregio
Copy link
Contributor Author

@DonJayamanne This is specifically for startup, not necessarily execution once it's already connected so maybe a mix of #7849 and #7134..

@DonJayamanne
Copy link
Contributor

DonJayamanne commented Oct 26, 2021

#7849 is startup, so is #7134, (both are about startup).

@DonJayamanne
Copy link
Contributor

Closing as a dup of #7849, #7134,

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug perf Performance issues
Projects
None yet
Development

No branches or pull requests

2 participants