Pods allow easy customization of auto shutdown interval when inactive.
By default, Pods automatically shut off after 1 hour of no network activity.
In the context of Latch Pods, network activity refers to the of inbound or outbound data transfer over the network interface associated with the instance. Some examples of network activity are:
Data retrieval: If your code within JupyterLab or RStudio interacts with remote data sources, such as querying databases, making API requests, or accessing files from remote locations, network activity will occur when the code sends requests over the network to fetch the required data.
Package installation or updates: If you install or update packages from remote package repositories within JupyterLab or RStudio, network activity will be required to download the packages and dependencies.
Collaborative features: Both JupyterLab and RStudio support collaborative features, allowing multiple users to work on the same project or document simultaneously. In such cases, network activity occurs as the server synchronizes changes made by different users, allowing real-time collaboration.
It’s important to note that network activity in JupyterLab or RStudio depends on the specific code and operations performed within the environment. If the code and computations are self-contained or focused on local data analysis, network activity may be minimal or non-existent during the execution.
If you notebook contain code blocks that take multiple hours to locally execute, it is recommended that you increase the auto-shutdown duration to allow sufficient time for the code to finish running.
To change the Pod’s auto shutoff interval, select the pod of interest, and click Manage Pod to navigate to the Pod’s Settings page.
When auto shutdown is enabled, the minimum delay before the Pod can be shut down is 15 minutes.
If Pod’s auto shutdown is disabled, the Pod will always be running. This behaviour is often undesirable, except in the case where you want an always-on Pod for running an application server or long-running scripts.
