Methods › Natural Language Processing › Synthesized Attention Mechanisms › Factorized Random Synthesized Attention
Factorized Random Synthesized Attention
Introduced by Yi Tay et al. in Synthesizer: Rethinking Self-Attention in Transformer Models
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
Factorized Random Synthesized Attention, introduced with the Synthesizer architecture, is similar to factorized dense synthesized attention but for random synthesizers. Letting R being a randomly initialized matrix, we factorize R into low rank matrices R₁, R₂ ∈ℝ^(l xk) in the attention function:
Y = Softmax(R₁R₂ᵀ)G(X) .
Here G(.) is a parameterized function that is equivalent to V in Scaled Dot-Product Attention.
For each head, the factorization reduces the parameter costs from l² to 2(lk) where k << l and hence helps prevent overfitting. In practice, we use a small value of k = 8.
The basic idea of a Random Synthesizer is to not rely on pairwise token interactions or any information from individual token but rather to learn a task-specific alignment that works well globally across many samples.
In Syntology name not resolved (unknown_name). The lookup matched no method, paper or venue by this name; that asserts nothing about whether code exists.
Near matches the lookup lists, each a different name: Random Attention; Random Attention (RA); Randomized Attention (RA); Linear Randomized Attention (LARA); Random Attention Prior Kernel (RAPK); FSAM (Factorized Self-Attention Module); factorized attention-based transformer model; MFPI-random.
Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.
Papers archive 2025-07-28
archive papers tagged: 1 · with a code link: 1 · where Syntology ran a sample: 1 (1 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (1 of 1 tagged: 1 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Page 1 of 1: paper 1 of 1, newest first by the archive's date (ties by slug), in archive order.
Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.
-
Synthesizer: Rethinking Self-Attention in Transformer Models 2 May 2020 · 1 repository · arXiv:2005.00743Syntology 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result (of 1 harvested sample)
Tasks archive 2025-07-28
10 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.
Usage over time archive 2025-07-28
Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).
Categories archive 2025-07-28
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