The default behavior in SageMaker Studio is for it to start a kernel whenever you open an existing notebook that has been assigned a kernel before.
In my discussions with customers, I have been asked several times how one could modify this behaviour. Automatic kernel starts cannot be cancelled as the kernel is being spun up, hence the SageMaker Studio user has to wait for the kernel to be provisioned. This can be time consuming and cost ineffective for very big instance types.
This script configures page settings for your Jupyter Server in order to disable automatic startup of kernels on notebook access.
The default behavior in SageMaker Studio is for it to start a kernel whenever you open an existing notebook that has been assigned a kernel before.
In my discussions with customers, I have been asked several times how one could modify this behaviour. Automatic kernel starts cannot be cancelled as the kernel is being spun up, hence the SageMaker Studio user has to wait for the kernel to be provisioned. This can be time consuming and cost ineffective for very big instance types.
This script configures page settings for your Jupyter Server in order to disable automatic startup of kernels on notebook access.
See LinkedIn post with research here: https://www.linkedin.com/pulse/draft/AgG6vX4-n1JanQAAAYTDlz6iV1BNYLwjfg5iYzWlEAqdPst2IDr4bvokxw3Fh3jmKuUdfDk