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
:::image type="content" source="./media/concept-designer/designer-drag-and-drop.gif" alt-text="GIF of a building a pipeline in the designer." lightbox= "./media/concept-designer/designer-drag-and-drop.gif":::
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-debug-pipeline-failure.md
+1-8Lines changed: 1 addition & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ services: machine-learning
9
9
ms.service: machine-learning
10
10
ms.subservice: core
11
11
ms.topic: how-to
12
-
ms.date: 12/22/2022
12
+
ms.date: 05/27/2023
13
13
ms.custom: designer, event-tier1-build-2022
14
14
---
15
15
@@ -25,9 +25,6 @@ This article introduces how to use the pipeline job page to debug machine learni
25
25
> For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
26
26
27
27
28
-
29
-
30
-
31
28
## Using outline to quickly find a node
32
29
33
30
In pipeline job detail page, there's an outline left to the canvas, which shows the overall structure of your pipeline job. Hovering on any row, you can select the "Locate" button to locate that node in the canvas.
@@ -58,8 +55,6 @@ If your pipeline fails or gets stuck on a node, first view the logs.
58
55
59
56
If you don't see those folders, this is due to the compute run time update isn't released to the compute cluster yet, and you can look at **70_driver_log.txt** under **azureml-logs** folder first.
60
57
61
-
62
-
63
58
## Compare different pipelines to debug failure or other unexpected issues (preview)
64
59
65
60
Pipeline comparison identifies the differences (including topology, component properties, and job properties) between multiple jobs. For example you can compare a successful pipeline and a failed pipeline, which helps you find what modifications make your pipeline fail.
@@ -150,8 +145,6 @@ To share your comparison results select **Share** and copying the link. For exam
150
145
151
146
:::image type="content" source="./media/how-to-debug-pipeline-failure/share.png" alt-text="Screenshot showing the share button and the link you should copy." lightbox= "./media/how-to-debug-pipeline-failure/share.png":::
152
147
153
-
154
-
155
148
## Next steps
156
149
157
150
In this article, you learned how to debug pipeline failures. To learn more about how you can use the pipeline, see the following articles:
Copy file name to clipboardExpand all lines: articles/machine-learning/how-to-debug-pipeline-performance.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ services: machine-learning
9
9
ms.service: machine-learning
10
10
ms.subservice: core
11
11
ms.topic: how-to
12
-
ms.date: 04/28/2023
12
+
ms.date: 05/27/2023
13
13
ms.custom: designer, pipeline UI
14
14
---
15
15
# View profiling to debug pipeline performance issues (preview)
@@ -32,14 +32,12 @@ To enable this feature:
32
32
1. On the Jobs page, select the job name and enter the job detail page.
33
33
1. In the action bar, select **View profiling**. Profiling only works for root level pipeline. It will take a few minutes to load the next page.
34
34
35
-

36
-
37
-
35
+
:::image type="content" source="./media/how-to-debug-pipeline-performance/view-profiling.png" alt-text="Screenshot showing the pipeline at root level with the view profiling button highlighted." lightbox= "./media/how-to-debug-pipeline-performance/view-profiling.png":::
38
36
39
37
1. After the profiler loads, you'll see a Gantt chart. By Default the critical path of a pipeline is shown. A critical path is a subsequence of steps that determine a pipeline job's total duration.
40
38
41
-

42
-
39
+
:::image type="content" source="./media/how-to-debug-pipeline-performance/critical-path.png" alt-text="Screenshot showing the Gantt chart and the critical path." lightbox= "./media/how-to-debug-pipeline-performance/critical-path.png":::
40
+
43
41
1. To find the step that takes the longest, you can either view the Gantt chart or the table below it.
44
42
45
43
In the Gantt chart, the length of each bar shows how long the step takes, steps with a longer bar length take more time. You can also filter the table below by "total duration". When you select a row in the table, it shows you the node in the Gantt chart too. When you select a bar on the Gantt chart it will also highlight it in the table.
@@ -48,8 +46,7 @@ To enable this feature:
48
46
49
47
If you select the log icon next the node name it opens the detail page, which shows parameter, code, outputs, logs etc.
50
48
51
-

52
-
49
+
:::image type="content" source="./media/how-to-debug-pipeline-performance/detail-page-from-log-icon.png" alt-text="Screenshot highlighting the log icon and showing the detail page." lightbox= "./media/how-to-debug-pipeline-performance/detail-page-from-log-icon.png":::
53
50
54
51
If you're trying to make the queue time shorter for a node, you can change the compute node number and modify job priority to get more compute resources on this one.
55
52
@@ -86,7 +83,7 @@ Status and definitions:
86
83
87
84
To export the table, select **Export CSV**.
88
85
89
-

86
+
:::image type="content" source="./media/how-to-debug-pipeline-performance/export-csv.png" alt-text="Screenshot show export csv in profiling." lightbox= "./media/how-to-debug-pipeline-performance/export-csv.png":::
Copy file name to clipboardExpand all lines: articles/machine-learning/v1/concept-designer.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Azure Machine Learning designer is a drag-and-drop interface used to train and d
31
31
- To get started with the designer, see [Tutorial: Train a no-code regression model](tutorial-designer-automobile-price-train-score.md).
32
32
- To learn about the components available in the designer, see the [Algorithm and component reference](../algorithm-module-reference/module-reference.md).
:::image type="content" source="../media/concept-designer/designer-drag-and-drop.gif" alt-text="GIF of a building a pipeline in the designer." lightbox= "../media/concept-designer/designer-drag-and-drop.gif":::
35
35
36
36
The designer uses your Azure Machine Learning [workspace](../concept-workspace.md) to organize shared resources such as:
37
37
@@ -55,7 +55,7 @@ Use a visual canvas to build an end-to-end machine learning workflow. Train, tes
55
55
+ Publish a **batch inference pipeline** to make predictions on new data by using a previously trained model.
56
56
+[Deploy](#deploy) a **real-time inference pipeline** to an online endpoint to make predictions on new data in real time.
57
57
58
-

58
+
:::image type="content" source="../media/concept-designer/designer-workflow-diagram.png" alt-text="Workflow diagram for training, batch inference, and real-time inference in the designer.":::
59
59
60
60
## Pipeline
61
61
@@ -88,9 +88,9 @@ A machine learning data asset makes it easy to access and work with your data. S
88
88
89
89
A component is an algorithm that you can perform on your data. The designer has several components ranging from data ingress functions to training, scoring, and validation processes.
90
90
91
-
A component may have a set of parameters that you can use to configure the component's internal algorithms. When you select a component on the canvas, the component's parameters are displayed in the Properties pane to the right of the canvas. You can modify the parameters in that pane to tune your model. You can set the compute resources for individual components in the designer.
91
+
A component may have a set of parameters that you can use to configure the component's internal algorithms. When you select a component on the canvas, the component's parameters are displayed in the Properties pane to the right of the canvas. You can modify the parameters in that pane to tune your model. You can set the compute resources for individual components in the designer.
:::image type="content" source="../media/concept-designer/properties.png" alt-text="Screenshot showing the component properties.":::
94
94
95
95
96
96
For some help navigating through the library of machine learning algorithms available, see [Algorithm & component reference overview](../component-reference/component-reference.md). For help with choosing an algorithm, see the [Azure Machine Learning Algorithm Cheat Sheet](algorithm-cheat-sheet.md).
0 commit comments