Skip to content
New issue

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

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

Already on GitHub? # to your account

The loading speed is too slow when opening the page for the first time #17188

Closed
nslqd1239 opened this issue Jan 18, 2025 · 1 comment
Closed
Labels
bug status:Needs Triage Applied to new issues that need triage

Comments

@nslqd1239
Copy link

Description

We tried to install jupyterlab in a container for users to use, but found that when opening the jupyter page for the first time, a lot of front-end resources need to be loaded, which takes a lot of time to complete the page loading, about 25 seconds. Of course, this also depends on my wifi speed not being fast enough, but I have also tested it in a good network environment, and it is still much slower than opening a regular website.

I have tried some methods, but they have not been effective in solving:

  1. Removed custom plugins
  2. Adjusted the system configuration of jupyterlab (although my understanding may not be comprehensive enough)
  3. Attempted Jupyter Hub

May I ask if there are any configuration options that can prevent unnecessary front-end resources from loading when first opened, or change unused resources to lazy loading, or support pulling these front-end resources from specified CDNs to improve speed.

Hope you can help answer, thank you!

Context

  • Operating System and version: Ubuntu22.04
  • Browser and version: 131.0.6778.266
  • JupyterLab version: 4.0.0

Image

@nslqd1239 nslqd1239 added the bug label Jan 18, 2025
@jupyterlab-probot jupyterlab-probot bot added the status:Needs Triage Applied to new issues that need triage label Jan 18, 2025
@RRosio
Copy link
Contributor

RRosio commented Jan 21, 2025

Thank you for opening this issue @nslqd1239! This has been reported previously, so I will close this issue as a duplicate of open issues such as: #14124, and #5862. Let's continue the discussion one of those existing issues!

As an additional note, per triage: @krassowski points out that there have been some improvements that do not solve the issue entirely but do improve the situation for performance since JupyterLab 4.0.0 (for example: #15334). Please feel free to try the latest version out!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug status:Needs Triage Applied to new issues that need triage
Projects
None yet
Development

No branches or pull requests

2 participants