Configure a dev environment
Set CPU, memory, GPU, and storage options when launching a dev environment in Developer Workspace.
You configure a dev environment's resources at launch time. The settings you choose determine how much compute and storage the dev environment has while it runs.
CPU and memory
Set Minimum CPU and Minimum Memory Gi in the creation form. These are the minimum guaranteed resources for your dev environment.
| Workload type | Suggested CPU | Suggested memory |
|---|---|---|
| Light data exploration | 1 | 4 Gi |
| Standard data science | 2–4 | 8–16 Gi |
| Large dataset processing | 8+ | 32+ Gi |
Start with a smaller allocation and relaunch the dev environment with higher resources if your workload needs more.
GPU
- Expand Advanced Options in the creation form.
- Set the number of GPUs under GPUs.
- Select the GPU vendor from the dropdown.
GPU hardware required
GPUs are only available if your BullSequana AI installation includes GPU-enabled hardware. If the GPU field is missing or your dev environment fails to start after requesting GPUs, contact your workspace administrator.
Storage volumes
Workspace volume
The workspace volume is your home directory. A new 5 Gi volume is created automatically unless you change the size or attach an existing volume.
To increase the size, change the value in the Workspace Volume section before selecting LAUNCH. You cannot resize a volume after it is created.
Data volumes
Data volumes let you attach additional storage to your dev environment, for example a shared dataset volume.
To add a data volume:
- In the Data Volumes section, select Add new volume to create a fresh volume, or Attach existing volume to mount one that already exists.
- Set the mount path. This is the directory where the volume appears inside your dev environment (for example,
/home/jovyan/data). - Select LAUNCH.
You can attach multiple data volumes to a single dev environment.
Persisting data between sessions
Your workspace volume persists when you stop and restart a dev environment. Data volumes also persist if you re-attach them when relaunching a dev environment.
Files saved outside your mounted volumes are lost when the dev environment is deleted.