简体中文 · English
SlimPer: Long-sequence personalized ranking with a fixed knowledge base¶
Fidelity: core-mechanism reproduction. Trains layered Select–Match–Refine, a fixed-capacity knowledge base, and request-only sharing of user tokens. History length and modalities are scaled down.
Paper information¶
| Field | Details |
|---|---|
| Paper | arXiv 2607.12281 |
| Institution | Meta Platforms, Inc. |
| First public release | 2026-07-14 (arXiv v1) |
| Author code | No official or author-released code found in the paper (checked 2026-08-09). |
| Local adapter or method key | slimper |
| Local reproduction code | src/auto_research/reproductions/slimper/ |
Original paper summary¶
Background and main changes¶
A generative Transformer keeps intermediate state for every token, whereas recommendation ranking returns only a few user-item relevance scores. SlimPer replaces per-layer N×d history state with a fixed K×d knowledge base. Each layer revisits raw sparse and sequence tokens, selects relevant evidence, explicitly matches it with knowledge templates, and refines the knowledge base. User tokens are encoded once per request and shared across all candidates.
flowchart LR
U[shared raw user tokens N×d] --> S1[Select: KB queries raw tokens]
I[item / cross features] --> K0[fixed knowledge base K×d]
K0 --> S1
S1 --> M[Match: q×t relevance]
K0 --> M
M --> R[Refine KB]
R --> K1[next K×d knowledge base]
K1 --> S2[next SlimPer layer]
K1 --> P[task logits]
Key figure from the paper¶
Figure 2: The core architecture, its main modules, and their connections. From the paper; copyright belongs to the authors. Click for the source.
Core equations¶
Per-layer compute is \(O(KN)\) with fixed intermediate state \(O(LK)\), versus \(O(N^2)\) compute and \(O(LN)\) state for full-sequence attention.
Offline and online results¶
For Reels with 2k events, reshare NE -0.51%, QPS +11.0%, memory -9.32%; for Feed with 1k events, memory -18.12%. The paper reports 8×–25× fewer actual FLOPs. SlimPer reached full traffic in Instagram Reels and Feed, with statistically significant engagement gains, no ecosystem guardrail regressions, and nearly neutral GPU capacity. Exact online lifts are not disclosed; aggregate top-line impact is about 10× a typical statistically significant launch. This project accepts full-traffic evidence as an explicit user-approved exception to its industrial inclusion gate.
Local reproduction¶
Local comparison: A parameter-matched 6-layer full-sequence Transformer (138,337 parameters) is compared with 3-layer SlimPer (145,027 parameters). Relative NDCG@10 is
+1.29%.
MovieLens-100K uses 220 users, 360 items, 32-event histories, matched examples and optimizer, and 120 steps. SlimPer Hit@10 +14.29%, attention-score elements -94.12%, and layer intermediate-state elements -87.88%. Full-catalog inference encodes user tokens once per request. See metrics/movielens-100k-seed42.json.
Scope¶
MovieLens item, genre, and sequence features replace Instagram sparse, dense, and multimodal features. The run uses 32 instead of 1k–10k+ events, and AdamW instead of Shampoo. It does not reproduce production kernels, multi-task heads, or measured QPS, reporting analytical attention and intermediate-state element counts only.
