You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/machine-learning/compare-azure-ml-to-studio-classic.md
+10-5Lines changed: 10 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,27 +12,32 @@ ms.date: 03/24/2020
12
12
13
13
# Azure Machine Learning vs Machine Learning Studio (classic)
14
14
15
-
Azure Machine Learning provides both SDKs **and** the "drag-and-drop" designer to build machine learning models. Studio (classic) only offers a standalone drag-and-drop experience.
15
+
You can use both Azure Machine Learning and Machine Learning Studio (classic) to build and deploy machine learning models. In this article, you learn the differences between the two offerings.
16
16
17
-
We recommend that new users start with Azure Machine Learning for a wide range of cutting-edge machine learning tools. For more information on what Azure Machine Learning has to offer, see [What is Azure Machine Learning?](overview-what-is-azure-ml.md)
17
+
Azure Machine Learning provides both SDKs **and** the "drag-and-drop" designer to build, deploy, and manage machine learning models. Studio (classic) only offers a standalone drag-and-drop experience.
18
+
19
+
We recommend that new users start with Azure Machine Learning for a comprehensive set of the most cutting-edge machine learning tools. For more information on what Azure Machine Learning has to offer, see [What is Azure Machine Learning?](overview-what-is-azure-ml.md)
18
20
19
21
## Quick comparison
20
22
23
+
The following table summarizes some of the key differences betwee Azure Machine Learning and Studio (classic):
24
+
21
25
|| Azure Machine Learning | Machine Learning Studio (classic) |
22
26
|---| --- | --- |
23
-
| Drag and drop interface |Yes - [Azure Machine Learning designer (preview)](concept-designer.md)|Yes|
27
+
| Drag and drop interface |Supported - [Azure Machine Learning designer (preview)](concept-designer.md)|Supported|
24
28
| Experiment | Scale with compute target | Scalable (10-GB training data limit) |
25
29
| Training compute targets | Supports Azure Machine Learning compute (GPU or CPU) and Notebook VMs.<br/>([Other computes supported in SDK](concept-compute-target.md#train))| Proprietary compute target, CPU support only|
26
30
| Inferencing compute targets | Azure Kubernetes Service and AML Compute <br/>([Other computes supported in SDK](how-to-deploy-and-where.md)) | Proprietary web service format, not customizable |
27
31
| ML Pipeline |[Supported](concept-ml-pipelines.md)| Not supported |
28
32
| MLOps |[Configurable deployment](concept-model-management-and-deployment.md) - model, pipeline, and dataset versioning and tracking | Basic model management and deployment |
29
33
| Model format | Standard format depending on training job type | Proprietary format, Studio (classic) only |
30
-
| Automated model training and hyperparameter tuning |[Supported in the SDK and visual workspace](concept-automated-ml.md)| No |
34
+
| Automated model training and hyperparameter tuning |[Supported in the SDK and visual workspace](concept-automated-ml.md)| Not supported |
35
+
| Data drift detection |[Supported in SDK and visual workspace](how-to-monitor-datasets.md)| Not supported |
31
36
32
37
33
38
## Migrate from Machine Learning Studio (classic)
34
39
35
-
Currently, there's no way to migrate Studio (classic) experiments to Azure Machine Learning designer (preview). However, we'll provide a migration path after the designer becomes generally available. Until then, we encourage users to try the designer, which provides a familiar drag-and-drop experience with improved workflow **plus** scalability, version control, and enterprise security.
40
+
Currently, there's no way to migrate Studio (classic) assets to Azure Machine Learning designer (preview). However, we'll provide a migration path once the designer becomes generally available. Until then, we encourage users to try the designer, which provides a familiar drag-and-drop experience with improved workflow **plus** scalability, version control, and enterprise security.
0 commit comments