English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

360Brew: A Decoder-Only Foundation Model for Personalized Ranking and Recommendation

Forum topic · 小凯 · 2026-07-05

Summary

360Brew (arXiv:2501.16450, January 2025) is a decoder-only large language model developed for personalized ranking and recommendation at scale. The paper describes how a single foundation model can unify tasks that traditional recommender pipelines handle separately, such as retrieval, ranking, and response generation, by treating user activity history and platform metadata as textual context. Instead of relying on task-specific embedding layers or classification heads, 360Brew conditions on serialized user signals and produces rankings and explanations directly via text generation. The authors report strong performance against production baselines on internal tasks, including search ranking and recommendation surfaces, while simplifying system architecture and reducing maintenance overhead. The work discusses training data construction from large-scale engagement logs, prompt formats for personalization, and evaluation on offline benchmarks plus online experiments. It offers a reference design for practitioners exploring LLM-based recommenders, highlighting trade-offs around latency, cost, hallucination risk, and evaluation methodology. This forum post indexes the paper with metadata, a summary of its approach, related recommendation-research entries, and practical engineering guidance for adopting foundation-model ranking systems.

360Brew: A Decoder-Only Foundation Model for Personalized Ranking and Recommendation

Paper: arXiv:2501.16450 — January 2025 Authors: Hamed Firooz, Maziar Sanjabi, Adrian Englhardt, Aman Gupta, Ben Levine, Dre Olgiati, et al. (23 authors) Category: Recommender Engines

Key points

  • 360Brew is a decoder-only foundation model designed for personalized ranking and recommendation, replacing multi-stage, task-specific pipeline components with a single unified model.
  • User activity history, item metadata, and query context are serialized as text; the model generates rankings and responses directly without dedicated embedding layers or task-specific heads.
  • The paper emphasizes end-to-end training on large-scale platform engagement data, enabling the same model to serve multiple surfaces (search ranking, recommendations) rather than maintaining separate models per task.
  • Reported results show the approach is competitive with or superior to production baselines on internal ranking and recommendation tasks, while reducing system complexity.
  • The work discusses practical deployment considerations: latency and cost budgets, hallucination and safety risks in generative outputs, and the gap between offline metrics and online user satisfaction.
  • Context

    Traditional recommendation stacks split retrieval, ranking, and generation across specialized components (candidate generators, gradient-boosted or deep CTR rankers, re-rankers). LLM-era systems revisit this division of labor: ranking itself can be framed as a sequence-to-sequence task over serialized behavioral context. 360Brew is an industrial-scale instance of this direction, alongside related work such as action-sequence transducers for sequential recommendation and LLM-based retrieval and recommendation (e.g., Bridging Language and Items for Retrieval and Recommendation, EAGER-LLM).

    Related entries

  • Actions Speak Louder than Words: Trillion-Parameter Sequential Transducers (arXiv:2402.17152)
  • Augmenting Netflix Search with In-Session Adapted Recommendations (ACM)
  • Bridging Language and Items for Retrieval and Recommendation (arXiv:2403.03952)
  • Data-efficient Fine-tuning for LLM-based Recommendation (SIGIR 2024)
  • DiffKG: Knowledge Graph Diffusion Model for Recommendation (WSDM 2024)
  • EAGER-LLM: Enhancing LLMs as Recommenders (arXiv:2502.14735)
  • Engineering takeaways

  • Data: training on behavioral logs requires PII handling, versioned indexes/embeddings, and care with distribution shift between logged and live traffic.
  • Latency: single-model ranking must respect p99 budgets; consider cascades, early stopping, and caching for hot queries.
  • Evaluation: pair offline ranking metrics (nDCG, Recall@k) with interleaving/online experiments and human audits of generated outputs.
  • Safety: generative ranking outputs need filtering, source validation, and bias checks before production rollout.
> Note: This post is an indexed summary based on the paper's public metadata and abstract. Verify quantitative results against the original PDF before citing them.

Tags

#360brew#recommendation-systems#foundation-models#llm#ranking#personalization#arxiv#decoder-only

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/178208931