Papers › Long-Sequence Recommendation Models Need Decoupled Embeddings

Long-Sequence Recommendation Models Need Decoupled Embeddings

3 Oct 2024arXiv:2410.02604archive 2025-07-28

Ningya Feng, Junwei Pan, Jialong Wu, Baixu Chen, Ximei Wang, Qian Li, Xian Hu, Jie Jiang, Mingsheng Long

Lifelong user behavior sequences are crucial for capturing user interests and predicting user responses in modern recommendation systems. A two-stage paradigm is typically adopted to handle these long sequences: a subset of relevant behaviors is first searched from the original long sequences via an attention mechanism in the first stage and then aggregated with the target item to construct a discriminative representation for prediction in the second stage. In this work, we identify and characterize, for the first time, a neglected deficiency in existing long-sequence recommendation models: a single set of embeddings struggles with learning both attention and representation, leading to interference between these two processes. Initial attempts to address this issue with some common methods (e.g., linear projections -- a technique borrowed from language processing) proved ineffective, shedding light on the unique challenges of recommendation models. To overcome this, we propose the Decoupled Attention and Representation Embeddings (DARE) model, where two distinct embedding tables are initialized and learned separately to fully decouple attention and representation. Extensive experiments and analysis demonstrate that DARE provides more accurate searches of correlated behaviors and outperforms baselines with AUC gains up to 0.9% on public datasets and notable improvements on Tencent's advertising platform. Furthermore, decoupling embedding spaces allows us to reduce the attention embedding dimension and accelerate the search procedure by 50% without significant performance impact, enabling more efficient, high-performance online serving. Code in PyTorch for experiments, including model analysis, is available at https://github.com/thuml/DARE.

PaperPDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 9 code samples harvested from 1 repository linked to this paper: 9 ran (of which 2 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 4 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 9 ran (7 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 9 samples that ran has no recorded date.

thuml/dare officialmentioned in papermentioned on GitHubpytorchSyntology: 9 samples, 9 ran (2 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

9 samples harvested: 9 ran (of which 2 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 4 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

4ran · violated contract
2ran; the contract check could not run
3ran

Licence: 9 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from thuml/dare. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

thuml/dare official repository 9 samples, 9 ran (2 instrument-failed) · 0 unverified
AttentionModel in 8 papers model/base_model_pytorch.py ran fingerprinted no licence file found · pointer only · 5f13f35abd14dc82 · report fixture: returned AttentionModel · level recorded 2026-09-22
BaseModel in 92 papers model/base_model_pytorch.py ran no licence file found · pointer only · aa3f1f6def5c6e54 · report fixture: returned BaseModel · level recorded 2026-09-22
attention in 144 papers
census: 11 implementations from 10 papers, 7 distinct outputs across 5 buckets, one shared input per bucket
model/attention_pytorch.py ran no licence file found · pointer only · b5459f1f6325b000 · report fixture: signature q:Tensor/2/float, k:Tensor/3/float, v:Tensor/3/float, mask:Tensor/2/float, attn_func:str/0/str, return_scores:bool/0/bool, attn_model:callable/0/?, time_embedding_dim:int/0/int, use_time_mode:str/0/str, item_embedding_dim:int/0/int, soft_search:bool/0/bool · returned Tensor · level recorded 2026-09-24
calc_auc in 5 papers utils.py ran; the contract check could not run (RAISES) no licence file found · pointer only · 7873f0e1fa137cda · report fixture: signature raw_arr:list/1/list · returned float · level recorded 2026-09-24
gauss_normalize analysis/attention_accuracy_analysis/calc_learned.py ran · violated contract fingerprinted no licence file found · pointer only · f6dbcc7447051099 · report fixture: signature x:ndarray/1/float · returned ndarray · level recorded 2026-09-24
min_max_normalize in 7 papers analysis/attention_accuracy_analysis/calc_learned.py ran · violated contract fingerprinted no licence file found · pointer only · ef9170abf085609d · report fixture: signature x:ndarray/1/float · returned ndarray · level recorded 2026-09-24
normalization in 70 papers
census: 4 implementations from 6 papers, 4 distinct outputs across 3 buckets, one shared input per bucket this sample: bucket 2 of 3, arg 1: rank 1, kind float, dtype float64
analysis/attention_accuracy_analysis/calc_gt.py ran · violated contract fingerprinted no licence file found · pointer only · 86c7147edb17dd5d · report fixture: signature data:ndarray/1/float · returned ndarray · level recorded, date not recorded
pad_and_truncate preprocess/taobao_v4.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 9e51ba90ca7253fa · report fixture: signature seq:list/1/int, max_len:int/0/int · returned list · level recorded 2026-09-24
softmax in 240 papers
census: 53 implementations from 63 papers, 16 distinct outputs across 8 buckets, one shared input per bucket
analysis/attention_accuracy_analysis/calc_learned.py ran · violated contract fingerprinted no licence file found · pointer only · a585b44308980803 · report fixture: signature x:ndarray/1/float · returned ndarray · level recorded 2026-09-24

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Decoupled Attention and Representation Embeddings (DARE) (graph method: Decoupled Attention and Representation Embeddings (DARE)). 2 bricks; individually on a fixture: 2 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; every one of the 2 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

  1. BaseModel entry · level 1 · ran · aa3f1f6def5c6e54
  2. AttentionModel helper · level 1 · ran · 5f13f35abd14dc82

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2410.02604") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Recommendation Systems

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

AttentionSETSoftmax

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections