Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for DataSphere
    • Resolving project startup errors in DataSphere
    • Resolving the `Failed to deserialize variable` error
    • `Table of Contents` extension is missing in the JupyterLab extension catalog
    • Getting access to GPU g1.1 and higher configurations in DataSphere
    • Resolving issues with long code execution within DataSphere project cells
    • Resolving the `Servant not allocated` error when running code within DataSphere project cells
    • Resolving the `TestsFailure` error
    • Resolving the `Token authentication is enabled` error
    • Resolving errors with project access or login
    • Resolving the `KernelNotResponding The kernel died unexpectedly` error
    • Fixing the `ConnectTimeoutError` error when installing packages through pip
    • Resolving the `Device or resource busy` error

In this article:

  • Issue description
  • Solution
  • If the issue persists
  1. DataSphere
  2. Resolving issues with long code execution within DataSphere project cells

Troubleshooting long execution times within DataSphere project cells

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution
  • If the issue persists

Issue descriptionIssue description

  • When you try to run code from Jupyter notebook cells within a DataSphere project, you get the Preparing $CONF_NAME instance message, where $CONF_NAME is the name of the DataSphere computing resource configuration you are using.
  • Allocating a VM with the computing resource configuration selected in the DataSphere project properties takes a long time.
  • Code execution within DataSphere project cells takes much longer than expected.

SolutionSolution

Here are possible reasons for long execution times within DataSphere project cells:

  1. Long execution times in cells may may result from both the number of cells and the amount of code. Loading a full project with many cells can take a considerable amount of time. For projects with hundreds of cells, loading may take more than 10 minutes. If feasible, try to reduce the number of cells in your project or opt for a higher-performance computing configuration.

  2. When launching code in project cells for the first time, VMs with the relevant resource configuration are allocated and started. This operation also requires some time. You can use a more efficient configuration of computing resources to accelerate code launch in project cells.

If the issue persistsIf the issue persists

If the tips we provided did not help you resolve the issue, create a support ticket. Provide the following information in your ticket:

  1. DataSphere project URL (copy it from the address bar of your browser).
  2. Screenshots of the error and the piece of code that causes the error.
  3. Approximate date and time when the issue occurred.
  4. Information about third-party Docker images used in the project.
  5. Typical project loading time.

Was the article helpful?

Previous
Getting access to GPU g1.1 and higher configurations in DataSphere
Next
Resolving the `Servant not allocated` error when running code within DataSphere project cells
© 2025 Direct Cursus Technology L.L.C.