Help Center/ ModelArts/ ModelArts User Guide (Standard)/ Using Notebook for AI Development and Debugging/ Using a Notebook Instance for AI Development Through JupyterLab/ Upgrading JupyterLab
Updated on 2026-05-07 GMT+08:00
View PDF
Share

Upgrading JupyterLab

To enhance the usability of notebook, JupyterLab has been upgraded to version 4.4.10 (stable version in 2025). This major leap from the 2021 legacy version (3.2.3) significantly optimizes performance and startup speed. Key improvements include a rebuilt editor, enhanced debugging and collaboration tools, a more stable ecosystem, and comprehensive refinements to the interactive experience and memory efficiency. Hope you enjoy the upgrade.

Notes

Support for creating new notebook instances using JupyterLab 3.2.3 will be discontinued in April 2026. Additionally, technical support, including updates for new features, vulnerability/issue fixes, patch upgrades, service ticket guidance, and online troubleshooting, will no longer be provided. These services will no longer be applicable to the O&M assurance of ModelArts.

JupyterLab 4.3.1

This version has significantly improved user experience, functions, and performance. The following table lists the main updates. For further information, see JupyterLab Documentation.

Table 1 Feature updates

Function Module

Description

Workspaces

You can create multiple workspaces to organize and manage different projects and files, improving project management efficiency.

Launcher creation toolbar

Added a toolbar for function access and convenient operations.

Theme framework optimization

Optimized the theme framework to enhance the theme flexibility and compatibility. You can customize the GUI as required.

Configuration page optimization

Optimized user experience on the configuration page for easier use.

Performance optimization and debugging enhancement

Fully optimized the system performance and enhanced the debugging function to improve the development experience.

Code editor enhancement

Improved the code editor by adding new functions and optimizing performance to enhance the coding experience.

Search function enhancement

Enhanced the search function for quicker and more accurate search.

Performance enhancement

Improved the overall performance, system response speed, and system stability.

Custom CSS style sheets

Custom CSS style sheets can be used to adjust the GUI appearance to meet personalized requirements.

Markdown charts

Charts can be used in Markdown to facilitate document writing.

Virtual scroll bar

Introduced the virtual scroll bar to improve the scrolling experience of large files or a large amount of content.

Workspace UI

Improved the workspace UI to provide better visual effect and operation experience and enhance UI friendliness.

File access records

You can view recently opened and closed files to quickly access common files and improve work efficiency.

Keyboard shortcuts improvement

Keyboard shortcuts are improved for higher operation efficiency and convenience.

Upgrading JupyterLab

You can upgrade JupyterLab in either of the following ways:

Method 1: Stopping a Notebook Instance and Upgrading JupyterLab

After a notebook is stopped, only the data stored in /home/ma-user/work is retained. To save the development environment, save its settings as an image. For details, see Method 2: Saving a Notebook Instance and Upgrading JupyterLab.

If your notebook uses EVS for storage, EVS billing per GB continues even after stopping the instance until you delete it. For details about the billing, see Billing Item > Development Environment.

  1. Stop the notebook instance.
    1. Log in to the ModelArts console. In the navigation pane on the left, choose Development Workspace > Notebook.
    2. On the Notebook page, click Stop in the Operation column of the target instance.
    3. In the displayed dialog box, read the message and click OK.

      When the status of the notebook instance changes to Stopped, the notebook instance has been stopped.

      Figure 1 Notebook instance status

  2. Upgrade JupyterLab.
    1. On the Notebook page, click Start in the Operation column of the stopped instance.
    2. In the displayed dialog box, set JupyterLab Version to 4.3.1, set Auto Stop as required, and click OK.
      Figure 2 Starting a notebook instance

  3. Check whether JupyterLab is upgraded.

    On the Notebook page, click the instance name. If JupyterLab 4.3.1 is displayed on the instance details page, JupyterLab has been upgraded.

    Figure 3 JupyterLab version

Method 2: Saving a Notebook Instance and Upgrading JupyterLab

After the image is saved, the default working directory is the / path in the root directory. All installed dependency packages will be retained in the saved image. However, content in persistent storage (the /home/ma-user/work directory) will not be included in the final container image. When you use VS Code for remote development, the plug-ins installed on the Server are retained.

  1. Save the image.
    1. Log in to the ModelArts console. In the navigation pane on the left, choose Development Workspace > Notebook.
    2. On the Notebook page, click Save Image in the Operation column of the running instance.
    3. On the displayed page, configure related information and click OK.
      Figure 4 Saving an image

      After the image is saved, the instance status changes to Running. You can view the image details on the Image Management page.

  2. Upgrade JupyterLab.
    1. In the navigation pane on the left, choose Resource Management > Images.
    2. In the Custom Images tab, locate the image saved in step 1.
    3. Click Create Notebook in the Operation column.
    4. On the displayed page, set JupyterLab Version to 4.3.1, set other parameters as required, and click Create Now.

      When the status of the notebook instance changes to Running, the notebook instance has been created.

  3. Check whether JupyterLab is upgraded.

    On the Notebook page, click the instance name. If JupyterLab 4.3.1 is displayed on the instance details page, JupyterLab has been upgraded.

    Figure 5 JupyterLab version