Merge pull request #222084 from lebaro-msft/patch-11

Improving session management documentation

Author: 19BMG00

articles/machine-learning/how-to-access-terminal.md

@@ -63,7 +63,6 @@ Access all Git operations from the terminal. All Git files and folders will be s
 
 To integrate Git with your Azure Machine Learning workspace, see  [Git integration for Azure Machine Learning](concept-train-model-git-integration.md).
 
-
 ## Install packages
 
  Install packages from a terminal window. Install Python packages into the **Python 3.8 - AzureML** environment.  Install R packages into the **R** environment.
@@ -79,7 +78,7 @@ Or you can install packages directly in Jupyter Notebook, RStudio, or Posit Work
 ## Add new kernels
 
 > [!WARNING]
->  While customizing the compute instance, make sure you do not delete the **azureml_py36** or **azureml_py38** conda environments.  Also do not delete **Python 3.6 - AzureML** or **Python 3.8 - AzureML** kernels. These are needed for Jupyter/JupyterLab functionality.
+> While customizing the compute instance, make sure you do not delete the **azureml_py36** or **azureml_py38** conda environments.  Also do not delete **Python 3.6 - AzureML** or **Python 3.8 - AzureML** kernels. These are needed for Jupyter/JupyterLab functionality.
 
 To add a new Jupyter kernel to the compute instance:
 
@@ -106,12 +105,14 @@ To add a new Jupyter kernel to the compute instance:
 Any of the [available Jupyter Kernels](https://github.com/jupyter/jupyter/wiki/Jupyter-kernels) can be installed.
 
 ### Remove added kernels
+
 > [!WARNING]
->  While customizing the compute instance, make sure you do not delete the **azureml_py36** or **azureml_py38** conda environments.  Also do not delete **Python 3.6 - AzureML** or **Python 3.8 - AzureML** kernels. These are needed for Jupyter/JupyterLab functionality.
+> While customizing the compute instance, make sure you do not delete the **azureml_py36** or **azureml_py38** conda environments.  Also do not delete **Python 3.6 - AzureML** or **Python 3.8 - AzureML** kernels. These are needed for Jupyter/JupyterLab functionality.
 
 To remove an added Jupyter kernel from the compute instance, you must remove the kernelspec, and (optionally) the conda environment. You can also choose to keep the conda environment. You must remove the kernelspec, or your kernel will still be selectable and cause unexpected behavior.
 
 To remove the kernelspec:
+
 1. Use the terminal window to list and find the kernelspec:
 
     ```shell
@@ -125,13 +126,14 @@ To remove the kernelspec:
     ```
 
 To also remove the conda environment:
+
 1. Use the terminal window to list and find the conda environment:
 
     ```shell
     conda env list
     ```
 
-3. Remove the conda environment, replacing ENV_NAME with the conda environment you'd like to remove:
+1. Remove the conda environment, replacing ENV_NAME with the conda environment you'd like to remove:
 
     ```shell
     conda env remove -n ENV_NAME
@@ -141,7 +143,11 @@ Upon refresh, the kernel list in your notebooks view should reflect the changes
 
 ## Manage terminal sessions
 
- Select **View active sessions** in the terminal toolbar to see a list of all active terminal sessions. When there are no active sessions, this tab will be disabled.
+Terminal sessions can stay active if terminal tabs are not properly closed. Too many active terminal sessions can impact the performance of your compute instance.
+
+Select **Manage active sessions** in the terminal toolbar to see a list of all active terminal sessions and shut down the sessions you no longer need.
+
+Learn more about how to manage sessions running on your compute at [Managing notebook and terminal sessions](how-to-manage-compute-sessions.md).
 
 > [!WARNING]
->  Make sure you close any unused sessions to preserve your compute instance's resources. Idle terminals may impact performance of compute instances.
+> Make sure you close any sessions you no longer need to preserve your compute instance's resources and optimize your performance.

articles/machine-learning/how-to-manage-compute-sessions.md

@@ -0,0 +1,49 @@
+---
+title: How to manage compute sessions
+titleSuffix: Azure Machine Learning
+description: Use the session management panel to manage the active notebook and terminal sessions running on a compute instance.
+services: machine-learning
+author: lebaro-msft
+ms.author: lebaro
+ms.reviewer: sgilley
+ms.service: machine-learning
+ms.subservice: core
+ms.topic: how-to
+ms.date: 12/21/2022
+# Customer intent: As a data scientist, I want to manage the notebook and terminal sessions on my compute instance for optimal performance.
+---
+
+# Manage notebook and terminal sessions
+
+Notebook and terminal sessions run on the compute and maintain your current working state.
+
+When you reopen a notebook, or reconnect to a terminal session, you can reconnect to the previous session state (including command history, execution history, and defined variables). However, too many active sessions may slow down the performance of your compute. With too many active sessions, you may find your terminal or notebook cell typing lags, or terminal or notebook command execution may feel slower than expected.
+
+There's a session management panel in the Azure Machine Learning studio that helps you manage your active sessions and optimize the performance of your compute instance. You can navigate to this session management panel from the compute toolbar of either a terminal tab or a notebook tab.
+
+> [!NOTE]
+> For optimal performance, we recommend you don’t keep more than six active sessions - and the fewer the better.
+
+:::image type="content" source="media/how-to-manage-compute-sessions/compute-session-management-panel.png" alt-text="Screenshot of compute session management panel.":::
+
+## Notebook sessions
+
+In the session management panel, you can select a linked notebook name in the notebook sessions section to reopen a notebook with its previous state.
+
+Notebook sessions are kept active when you close a notebook tab in the Azure Machine Learning studio. So, when you reopen a notebook you'll have access to previously defined variables and execution state - in this case, you're benefitting from the active notebook session.
+
+However, keeping too many active notebook sessions can slow down the performance of your compute. So, you should use the session management panel to shut down any notebook sessions you no longer need.
+
+Select **Manage active sessions** in the terminal toolbar to open the session management panel and shut down the sessions you no longer need. In the following image, you can see that the tooltip shows the count of active notebook sessions.
+
+:::image type="content" source="media/how-to-manage-compute-sessions/notebook-sessions-button.png" alt-text="Screenshot of notebooks sessions button in toolbar.":::
+
+## Terminal sessions
+
+In the session management panel, you can select on a terminal link to reopen a terminal tab connected to that previous terminal session.
+
+In contrast to notebook sessions, terminal sessions are terminated when you close a terminal tab. However, if you navigate away from the Azure Machine Learning studio without closing a terminal tab, the session may remain open. You should be shut down any terminal sessions you no longer need by using the session management panel.
+
+Select **Manage active sessions** in the terminal toolbar to open the session management panel and shut down the sessions you no longer need. In the following image, you can see that the tooltip shows the count of active terminal sessions.
+
+:::image type="content" source="media/how-to-manage-compute-sessions/terminal-sessions-button.png" alt-text="Screenshot of terminal sessions button in toolbar.":::

articles/machine-learning/media/how-to-manage-compute-sessions/compute-session-management-panel.png

@@ -423,6 +423,9 @@
             - name: Use a terminal
               displayName: git, github, clone, kernel, package
               href: how-to-access-terminal.md
+            - name: Manage compute sessions
+              displayName: sessions, terminal, kernel
+              href: how-to-manage-compute-sessions.md
         - name: Set up VS Code extension
           displayName: Visual Studio Code, VSCode, debug, bugs, remote, compute, instance
           href: how-to-setup-vs-code.md