Skip to content

Commit 7174e27

Browse files
Merge pull request #276728 from santiagxf/santiagxf-patch-1
Update how-to-log-view-metrics.md
2 parents fca8e30 + b010dab commit 7174e27

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/machine-learning/how-to-log-view-metrics.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -161,9 +161,9 @@ Metrics, as opposite to parameters, are always numeric, and they can be logged e
161161
162162
### Log metrics asynchronously
163163
164-
MLflow also allows logging of metrics in an asynchronous way. Asynchronous metric logging is particularly useful in cases with high throughput where large training jobs with hundreds of compute nodes might be running and trying to log metrics concurrently.
164+
MLflow also allows logging of metrics in an asynchronous way. Asynchronous metric logging is particularly useful in cases where large training jobs with tens of compute nodes might be running and trying to log metrics concurrently. It's also useful when a small number of nodes is trying to log a high number of metrics.
165165
166-
Asynchronous metric logging allows you to log metrics and wait for them to be ingested before trying to read them back. This approach scales to large training routines that log hundreds of thousands of metric values.
166+
Asynchronous metric logging allows you to log metrics immediately by avoiding waiting for them to materialize in the backend service. This approach scales to large training routines that log hundreds of thousands of metric values and it's the recommended approach.
167167
168168
MLflow logs metrics synchronously by default, however, you can change this behavior at any time:
169169
@@ -190,7 +190,7 @@ with mlflow.start_run():
190190
# (...)
191191
```
192192
193-
When you use `log_metric(synchronous=False)`, control is automatically returned to the caller once the operation is accepted; however, there is no guarantee at that moment that the metric value has been persisted.
193+
When you use `log_metric(synchronous=False)`, control is automatically returned to the caller once the operation is accepted; however, the value is not available for reading inmediately. Asynchronous logging of metrics does guarantee order and they are persisted with the timestamp of when they were logged.
194194
195195
> [!IMPORTANT]
196196
> Even with `synchronous=False`, Azure Machine Learning guarantees the ordering of metrics.

0 commit comments

Comments
 (0)