Papers › Efficiently Modeling Long Sequences with Structured State Spaces
Efficiently Modeling Long Sequences with Structured State Spaces
Albert Gu, Karan Goel, Christopher Ré
A central goal of sequence modeling is designing a single principled model that can address sequence data across a range of modalities and tasks, particularly on long-range dependencies. Although conventional models including RNNs, CNNs, and Transformers have specialized variants for capturing long dependencies, they still struggle to scale to very long sequences of $10000$ or more steps. A promising recent approach proposed modeling sequences by simulating the fundamental state space model (SSM) x′(t) = Ax(t) + Bu(t), y(t) = Cx(t) + Du(t), and showed that for appropriate choices of the state matrix A, this system could handle long-range dependencies mathematically and empirically. However, this method has prohibitive computation and memory requirements, rendering it infeasible as a general sequence modeling solution. We propose the Structured State Space sequence model (S4) based on a new parameterization for the SSM, and show that it can be computed much more efficiently than prior approaches while preserving their theoretical strengths. Our technique involves conditioning A with a low-rank correction, allowing it to be diagonalized stably and reducing the SSM to the well-studied computation of a Cauchy kernel. S4 achieves strong empirical results across a diverse range of established benchmarks, including (i) 91\% accuracy on sequential CIFAR-10 with no data augmentation or auxiliary losses, on par with a larger 2-D ResNet, (ii) substantially closing the gap to Transformers on image and language modeling tasks, while performing generation 60× faster (iii) SoTA on every task from the Long Range Arena benchmark, including solving the challenging Path-X task of length 16k that all prior work fails on, while being as efficient as all competitors.
In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2111.00396")
Code
Syntology Ran 28 of 55 code samples harvested from 8 repositories linked to this paper; 27 have no recorded run. Of those that ran: 2 ran · honoured contract; 1 ran · violated contract; 11 ran · our draft was wrong; 2 ran · fixture could not drive it; 12 ran with no contract checked.
By repository: official repository: 10 samples from 1 repository, 5 ran; community (archive-listed): 42 samples from 6 repositories, 20 ran; community: 2 samples from 1 repository, 2 ran; 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
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
55 samples harvested; 28 ran; 2 honoured the contract we drafted; 27 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.
Licence: 3 of the 55 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 8 repositories linked to this paper, official or community; each sample names its own and says which. Some samples are identical code Syntology first harvested from another repository; for those, this paper's copy is not located and its licence is not recorded. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.
Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.
855fe49867900076 · report
a0aad68e21728b6a · report
b7d9d94554e93b1b · report
e25911109ba29783 · report
d43b03a2d76a4e41 · report
2e1521f562fb37ea · report
b2fe7789636402f0 · report
7564850110a688c1 · report
9eb8abe7e31d874d · report
64dd93f539b06f8e · report
6e1825a893399540 · report
522a1fc1276ec144 · report
6c960a9598a04692 · report
9d310a2394e754b7 · report
1f674b4ed2ecc8cd · report
a19e25de29fbaae4 · report
5a5e28e0e6ccd2d2 · report
7bbdbc08ffa75119 · report
95f2fb2164162bdd · report
22730030e03982a4 · report
a6aaaac22e971146 · report
ada726a93c0d5dfc · report
818366932a065b68 · report
f1cab21ec84db199 · report
63d9be34f73a43ef · report
348275db42a37bee · report
b719a3ec912becb6 · report
e6971caf5e1cc5c1 · report
34b3f63a52000df0 · report
81a948ed6d1a963f · report
f3322f19b651f88b · report
e604fd0087c1b8f3 · report
e4f2a7408ee25578 · report
5c8e4f0e400a4956 · report
0d14eeb8e803d789 · report
67c82b9a05adebd0 · report
7d9920a7ef12302c · report
29e51ca431baa365 · report
b294cd8cde986e7e · report
b895231ad0d7eb03 · report
200d610a7e1bda69 · report
a9f0a96fb976b6ac · report
d637a7237715e2ea · report
2fbdf4a5c125f869 · report
c29c5241ff1d2f5a · report
fbd06741252dd8e2 · report
48664b31b86bdb2f · report
12ff0e50a74997cf · report
5b97d5371e044049 · report
2cebc3a83a8c3bc5 · report
f78db7b4e91ceafa · report
002674cddd8530fd · report
89b10a8b26bbb7ed · report
898daef1784ec4bd · report
f3449af8fae1d130 · report
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Language Modelling | WikiText-103 | S4 | Number of params | 249M | #45 of 89 | Archive leaderboard | report |
| Language Modelling | WikiText-103 | S4 | Test perplexity | 21.28 | #45 of 89 | Archive leaderboard | report |
| Sequential Image Classification | Sequential CIFAR-10 | S4 | Unpermuted Accuracy | 91.80% | #2 of 13 | Archive leaderboard | report |
| Sequential Image Classification | Sequential MNIST | S4 | Permuted Accuracy | 98.70% | #4 of 30 | Archive leaderboard | report |
| Sequential Image Classification | Sequential MNIST | S4 | Unpermuted Accuracy | 99.63% | #4 of 30 | Archive leaderboard | report |
| Speech Recognition | Speech Commands | S4 | Accuracy (%) | 98.32 | #3 of 3 | Archive leaderboard | report |
Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.
Methods
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