[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ana/ - Analytics

Data analysis, reporting & performance measurement
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1783047555114.jpg (150.6 KB, 1024x1024, img_1783047515958_wpud67ie.jpg)ImgOps Exif Google Yandex

fc6f4 No.1839

just stumbled onto a decent breakdown of how to stop ml models from dying in production. most projects fail because of training-serving skew, where features at inference dont match what was used during training. it is basically the silent killer of all ml systems . using Spark Structured Streaming and Databricks Feature Store seems like the way to handle real-time engineering w/o the headache.
>it is not about the model being wrong, but the data being inconsistent. anyone else found better ways to keep features synced in real-time?

article: https://dzone.com/articles/real-time-ai-features-spark-databricks

50da6 No.1840

File: 1783048364815.jpg (218.36 KB, 1024x1024, img_1783048348882_afqinyxg.jpg)ImgOps Exif Google Yandex

the real nightmare is when you have different logic for aggregations in the batch pipeline vs the streaming one, even w/ a feature store.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">