Stopping active runtimes
You should stop all active runtimes when you no longer need them to prevent consuming extra capacity unit hours (CUHs).
Jupyter notebook runtimes are started per user and not per notebook. Stopping a notebook kernel doesn’t stop the environment runtime in which the kernel is started because you could have started other notebooks in the same environment. You should only stop a notebook runtime if you are sure that no other notebook kernels are active.
Only runtimes that are started for jobs are automatically shut down after the scheduled job has completed. For example, if you schedule to run a notebook once a day for 2 months, the runtime instance will be activated every day for the duration of the scheduled job and deactivated again after the job has finished.
Project users with Admin role can stop all runtimes in the project. Users added to the project with Editor role can stop the runtimes they started, but can’t stop other project users’ runtimes. Users added to the project with the viewer role can’t see the runtimes in the project.
You can stop runtimes from:
- The Environment Runtimes page, which lists all active runtimes across all projects for your account, by clicking Administration > Environment Runtimes from the Watson Studio navigation menu.
- The Environments page of a project, which list the active runtimes for a specific project, by clicking the Environments tab for a project.
- The Environments tab when you click View notebook info in the notebook editor. You can stop the runtime under Runtime status.
Jupyter notebook idle timeout
Runtime idle times differ for the Jupyter notebook runtimes depending on your Watson Studio plan.
|Lite||- Idle stop time: 1 hour
- CUH limit: 50 CUHs
|Standard||- Idle stop time: 1 hour
- CUH limit: no limit
|Enterprise||- Idle stop time: 3 hours
- CUH limit: no limit
|- Idle stop time: 1 hour
- Maximum lifetime: 12 hours
Important: A runtime is started per user and not per notebook. Stopping a notebook kernel doesn’t stop the environment runtime in which the kernel is started because you could have started other notebooks in the same environment. Only stop a runtime if you are sure that no kernels are active.
Satellite runtime idle timeout
All Jupyter notebook environment runtimes on prebuilt Satellite locations are stopped after 3 hours of inactivity.
Spark idle timeout
All Spark runtimes are stopped after 3 hours of inactivity. The
Default Data Refinery XS runtime that is used when you refine data in Data Refinery is stopped after an idle time of 1 hour.
Spark runtimes that are started when a job is started, for example to run a Data Refinery flow or a notebook, are stopped when the job finishes.
GPU idle timeout
All GPU runtimes are automatically stopped after 1 hour of inactivity for Lite plan users and after 3 hours of inactivity for paid plan users.
RStudio idle timeout
An RStudio is stopped for you after an idle time of 2 hour.During this idle time, you will continue to consume CUHs for which you are billed. Long compute-intensive jobs are hard stopped after 24 hours.