๊ฐ€์ž… ํ›„ ์ดˆ๋Œ€ ๋งํฌ๋ฅผ ๊ณต์œ ํ•˜๋ฉด ๋™์˜์ƒ ์žฌ์ƒ ๋ฐ ์ดˆ๋Œ€ ๋ณด์ƒ์„ ๋ฐ›์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

cv usk
@cv_usk
AI / Software Research Notes AI Agent, LLMOps, MLOps, Software Architecture ๆŠ•็จฟใฏๅ€‹ไบบใฎๆ„่ฆ‹ใงใ™ใ€‚
๊ฐ€์ž… May 2026
282 ํŒ”๋กœ์ž‰ ์ค‘    431 ํŒฌ
TL;DR: Adding features to a recommender system is easy, but safely removing them is brutally hard. Pinterest built a production framework that automates that whole cleanup process. Title: FORTE: A Production Framework for Feature Evaluation and Deprecation in Industrial Recommender Systems URL: Key points ๐Ÿงฉ Adding a feature just needs a metric win, but removing one must not regress any metric, a built-in asymmetry that stalls cleanup โฑ๏ธ Daily perturbation experiments automatically track feature importance and rank stability over time ๐Ÿงช Grouped perturbation evaluates candidate feature sets together, catching interactions before costly retraining ๐Ÿš€ Pooled execution resolves all experiments for a model in a single distributed inference pass, cutting runtime 54x for 300 experiments ๐Ÿ”— Automated lineage tracking finds every downstream consumer model, making deprecation safe ๐Ÿ“‰ On the Pin Ranker model, removing 8 features cut parameters by 29.9%, boosted throughput 19.8-25.5%, and saved hundreds of thousands of dollars a year Feature removal infrastructure deserves as much engineering investment as feature addition, and this looks like a solid blueprint for it. #RecSys# #MLOps#
๋” ๋ณด๊ธฐ