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
Aim has a support for logging system metrics such as CPU/GPU/network/memory utilization. MLflow has just added a support for it in 2.8.0. It'd be nice to have FML support it, too. Maybe it'd already work out of the box with the new MLflow client, but most likely the special functionality for system metrics that exists in Aim UI (showing/hiding system metrics in one go) would still need some work.
We have just merged G-Research/fasttrackml-ui-aim#33 and #780 which add support for this feature. Once you enable system metrics logging via mlflow.enable_system_metrics_logging(), they will become available in both UIs, with the special treatment that you would expect from the Aim UI (hide/show, etc.).
This is currently only available on main (which is also tagged as edge for the container image), which we do not recommend for production use. Let us know if you would like us to backport this feature to our 0.4.x series!
Aim has a support for logging system metrics such as CPU/GPU/network/memory utilization. MLflow has just added a support for it in 2.8.0. It'd be nice to have FML support it, too. Maybe it'd already work out of the box with the new MLflow client, but most likely the special functionality for system metrics that exists in Aim UI (showing/hiding system metrics in one go) would still need some work.
From MLflow 2.8.0 release notes:
The text was updated successfully, but these errors were encountered: