Methods › Natural Language Processing › Transformers › Reformer

Reformer

20 papers tagged archive 2025-07-28

Introduced by Nikita Kitaev et al. in Reformer: The Efficient Transformer

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

Reformer is a Transformer based architecture that seeks to make efficiency improvements. Dot-product attention is replaced by one that uses locality-sensitive hashing, changing its complexity from O(L²) to O(LlogL), where L is the length of the sequence. Furthermore, Reformers use reversible residual layers instead of the standard residuals, which allows storing activations only once in the training process instead of N times, where N is the number of layers.

PaperSource

In Syntology repository known, no verified implementation (declared_code; repositories: 5 listed of 10 in the graph, strongest link: official). The lookup matched 'REFORMER' ignoring case. This answer is about arXiv:2001.04451, the paper the archive credits with this method.

Origin paper of this answer, arXiv:2001.04451 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 6 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; 5 where Syntology's instrument failed) · 2 unverified (of 8 harvested samples). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.

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: 20 · with a code link: 8 · where Syntology ran a sample: 2 (2 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 (2 of 20 tagged: 2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 20 of 20, 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.

Tasks archive 2025-07-28

20 shown of 48 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
Deep Learning2
Language Modelling2
Reinforcement Learning (RL)2
Sentence2
Survey2
Time Series2
Time Series Analysis2
Time Series Forecasting2
Attribute1
BIG-bench Machine Learning1
Binary Classification1
Click-Through Rate Prediction1
Computational Efficiency1
D4RL1
Data Augmentation1
Deblurring1
Decoder1
ECG Classification1
Face Recognition1
Facial Inpainting1

Usage over time archive 2025-07-28

Papers per year tagged with Reformer: 2020 to 2025, peak 6 6 0 2020: 6 papers 2020 2021: 4 papers 2021 2022: 4 papers 2022 2023: 1 paper 2023 2024: 3 papers 2024 2025: 2 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (20 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

Transformers

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