copilot struggling with large notebooks

[amunger]

Testing #210961

437KB file, but all input
spotify_noOutput.ipynb.txt

[jselis]

I had this problem too for many weeks. I read issue microsoft/vscode-jupyter#14459, based on that I disabled the IntelliCode extension, and problem was gone! --> but see edit below :-(
It happened mostly with large notebooks, but even with relatively small ones. Also debugging became almost impossible. I found especially large pandas DataFrames had an effect. For some reason it wanted to somehow analyze them each time, which took like 10 seconds before it executed a statement entered in the debug window below. Maybe this is a hint for the ones trying to solve this issue...

Edit: after a few hours working (with IntelliCode disabled) problem pops up again unfortunately. To execute a cell with just 4*6, it waits two seconds, then executes it. The only thing that helps in this situation is to restart VS Code entirely.

[jselis]

Seemed to have found a work-around while trying to follow the instructions to get a detailed CPU profile. After clicking the reload button (see screenshot), the problem disappeared. That means, the 2 seconds delay when executing the cell with "4 * 6" but also the slugginess when debugging that cell (breakpoint on that instruction 4 * 6)

Edit: same can be a achieved by F1 >Developer: Reload Window
Unfortunately it has the same effect as restarting VS Code, meaning I loose all variables in the Jupyter notebook.
There is also F1 >Developer: Reload Webviews. Next time I have the issue, will try this one (it doesn't destroy the variables), but doubt it will be enough to solve the delay.

[zjost]

Same. Only thing I have found that helps is closing VSCode and restarting, but this destroys all my state. It usually gives me another 30 min to an hour before it starts happening again. Very disruptive.

[SterlingYM]

Any update on this? I am experiencing this exact issue.

Version: 1.89.1 (Universal)
Commit: dc96b83
Date: 2024-05-07T05:14:24.611Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.1.0

[amunger]

This is getting fixed in the co-pilot repro and should be resolved when they release.

[arman258]

@amunger, any update on this? There were serval releases and pre-release updates on the copilot over the past two weeks. The issue happens at random times after a long period of use (microsoft/vscode-jupyter#14459)

I can't output perf in the developer menu when I encounter the problem, as I get the following error. Note this doesn't happen in the insider build of vscode.
Failed to save timeline: The request is not allowed by the user agent or the platform in the current context. (NotAllowedError)

But, I suspect the markdowns, too many cells with outputs, and cells with images and interactive plots (folium, plotly, etc) might be the root cause. The code execution in the cell after the problem happens seems to lag taking 2-5 seconds to complete, despite the output Jupyter log that shows the cell completed in a much, much shorter time (order of 0.1 s). Also, when the problem happens, Pylance syntax highlighting turns gray, and on the bottom status bar, it shows # cells # files to analyze, similar to microsoft/pylance-release#5748. When the status disappears, the syntax highlighting comes back, but the problem repeats if you execute any cell or scroll up and down.

[amunger]

this specific issue dealing with co-pilot appears to be fixed.

@arman258 I created #214040 for what is likely causing your performance issues - I experience similar behavior.