Codespaces¶
A codespace, similar to a repository or folder file tree structure, can contain any number of files and nested folders. Notebooks included in a codespace are represented as a persistent file (.ipynb), just like any of the other non-notebook files within a codespace. Unlike a DataRobot Notebook, which is treated as a single top-level notebook asset, a codespace can contain any number of notebooks. In addition to the persistent file storage, the codespace interface includes a file editor and integrated terminal for an advanced code development experience.
Within a codespace, you can open, view, and edit multiple notebook and non-notebook files at the same time. You can also execute multiple notebooks in the same container session (with each notebook running on its own kernel).
Because codespaces are Git-compatible, you can version your notebook files as well as non-notebook files in external Git repositories using the Git CLI.
| Topic | Description |
|---|---|
| Add a codespace | How to create a Codespace to store notebooks and associated files. |
| Codespace sessions | How to run and manage a DataRobot codespace session. |
| Notebook scheduling | The configuration options available for scheduling notebook runs. |
| Convert a notebook into a codespace | Learn about the options available for converting standalone notebooks into codespaces. |
Capabilities overview¶
Review the table below to understand the functional differences between a codespace and a DataRobot Notebook.
| Functionality | DataRobot Notebook | Codespace |
|---|---|---|
| Metadata (tags/description) | Yes (at the notebook level) | Yes (at the codespace level) |
| Git integration | No | Yes |
| Persistent file system | No | Yes |
| File editor | No | Yes |
| Terminal | Yes | Yes |
| Version control | Yes (built-in revision history) | Yes (controlled via external Git repos) |
| Environment variables | Yes (at the notebook level) | Yes (at the codespace level) |
| Session | Yes (one container session per notebook) | Yes (one container session per codespace) |
| Notebook scheduling | Yes | Yes |
Limits¶
The following limits are in place for codespaces.
| Limit | Value |
|---|---|
| File system limits | |
| Max upload size for an individual non-notebook file | 1 GB |
| Max size of each codespace file system | 20 GB |
| Session limits | |
| Max number of codespaces per org (default) | 50 |
| Max number of active codespace sessions | 5 |
| In-session limits | |
| Max size for an individual notebook (.ipynb) file | 25MB |
| Max number of open notebook files (in tabbed file editor) at the same time | 5 |