Methods › Natural Language Processing › Autoregressive Transformers › Routing Transformer

Routing Transformer

3 papers tagged archive 2025-07-28

Introduced by Aurko Roy et al. in Efficient Content-Based Sparse Attention with Routing Transformers

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

The Routing Transformer is a Transformer that endows self-attention with a sparse routing module based on online k-means. Each attention module considers a clustering of the space: the current timestep only attends to context belonging to the same cluster. In other word, the current time-step query is routed to a limited number of context through its cluster assignment.

PaperSource

Papers archive 2025-07-28

3 shown of 3, newest first. Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code; it is per sample and not a correctness claim.

Tasks archive 2025-07-28

12 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Attribute1
Decoder1
Form1
Image Generation1
Language Modeling1
Language Modelling1
Long Form Question Answering1
Open-Domain Dialog1
Open-Domain Question Answering1
Question Answering1
Text Generation1
Zero-Shot Learning1

Usage over time archive 2025-07-28

Papers per year tagged with Routing Transformer: 2020 to 2022, peak 1 1 0 2020: 1 paper 2020 2021: 1 paper 2021 2022: 1 paper 2022
Papers per year the archive tags with this method, by the paper's archive date (3 dated). Bars are counts, not a trend claim.

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

Autoregressive TransformersTransformers

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