~/talk

Sponsored Session: MLOps: Why DevOps Solutions Fall Short in the Machine Learning World

links:none on file
slides:none on file

Argues that DevOps tooling misses ML because people and artifacts differ: data scientists (not software engineers) prefer Jupyter-first workflows, need production data, and models encode implicit logic. Gives concrete failures: a platform replaced Uzi pipelines with microservices and adoption stalled for 300 data scientists; Kubeflow lacked a model registry. Details GitLab work: native Jupyter diffs (released 14.5), a built-in MLflow-compatible model experiments feature (saves artifacts, ties to CI), upcoming model registry, and limits like 10 GB SaaS artifact size and GPU-enabled runners.

AI-written summary · about

  1. 0:00MLOps introduction
  2. 1:05What is MLOps vs DevOps
  3. 2:37DevOps limits for data science
  4. 7:10Why DevOps falls short for machine learning
  5. 11:00ML development differences
  6. 16:18GitLab’s MLOps approach
  7. 19:06Unified MLOps vision
  8. 22:17Jupyter notebook reviews in GitLab
  9. 23:00Model experiment tracking in GitLab
  10. 24:23MLflow integration in GitLab
  11. 26:30Model registry in GitLab
  12. 27:57LLMOps challenges
  13. 30:05MLOps summary
  14. 32:21Q&A on data versioning
  15. 34:04Q&A on model registry
  16. 35:27Q&A on model deployment
  17. 36:35Q&A on LLM deployment
  18. 38:23Q&A on model explainability
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.