Idle Timeout for Notebooks
Wherobots Cloud has a new Idle Timeout feature to help you better manage your notebook runtime resources and optimize costs.
Benefits¶
- Improved resource utilization.
- Reduced potential costs associated with idle notebook runtimes.
- Greater control over your notebook runtime environment.
Key Features¶
- Customizable Timeout: You can now select an idle timeout duration for your notebook runtimes: 15 minutes, 45 minutes (default), or 120 minutes.
- Persistent User Settings: Your chosen idle timeout setting will be saved and automatically applied to your subsequent runtimes, even after logging out. This setting is specific to your Wherobots Account and does not affect the default settings for other members in your Wherobots Organization.
- Automatic Kernel Termination: When your notebook runtime remains inactive for the selected timeout period, the Jupyter kernel will automatically terminate to conserve resources.
- Notebook Instance Specific: Idle Timeout applies exclusively to Notebook Instances and does not work with Job Runs.
How Idle Timeout Works¶
Idle Timeout helps reduce costs by automatically scaling down inactive notebook runtimes to the minimum resources needed for your notebook instance during the idle period.
When a notebook exceeds the specified idle timeout threshold, the Jupyter kernel is terminated.
To resume work, you will need to restart the kernel and re-execute your notebook cells.
Try Idle Timeout now!
Important Considerations¶
- While Idle Timeout helps to reduce resource usage costs, you will still incur charges
for the minimum resources allocated to your notebook instance during the idle period.
- To completely release notebook resources and stop all related charges, you must destroy your active Notebook Instances.
Read the Documentation¶
To check out the new Idle Timeout step, refer to the updated instructions in Open a Notebook.