-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Scrolling (and rendering in general) is extremely slow #147253
Comments
@zareami10 thanks for your feedback. It would be great if we can get more information to troubleshoot this issue. It seems there are multiple issues:
|
I'm not really aware of the internals of the extension, can you please elaborate? Because it's bad enough to hinder working with any medium-sized notebooks, and I end up switching to the browser.
Sure, but about the very high CPU-usage, I believe it mostly happens when there are outputs being shown/updated as the notebook runs. |
Do you mind running following commands to help collect logs for the slowness you are seeing?
Does the CPU go high when you are using the browser or it only happens with VS Code? Any pattern of the code you are running? |
I have attached a profile on a kinda low-end hardware. But the situation is the same on stronger machines. Will profile on another machine with a dGPU too. |
This is the other profilng: Also no it only happens in Code. And my notebooks aren't really anything specific. |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Ever since the release of the new jupyter version, the performance of the extension has dropped dramatically. Scrolling is laggy, rendering outputs eats the CPU and even the progress bar can be 10fps per second with any notebook larger than a couple of cells.
And this is not corner case issue, I have had this problem on many different machines and even different OSes.
In comparison jupyter on a browser is at least 20 times faster/smoother.
The text was updated successfully, but these errors were encountered: