Methods › Reinforcement Learning › Replay Memory › Prioritized Experience Replay

Prioritized Experience Replay

138 papers tagged archive 2025-07-28

Introduced by Tom Schaul et al. in Prioritized Experience Replay

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

Prioritized Experience Replay is a type of experience replay in reinforcement learning where we more frequently replay transitions with high expected learning progress, as measured by the magnitude of their temporal-difference (TD) error. This prioritization can lead to a loss of diversity, which is alleviated with stochastic prioritization, and introduce bias, which can be corrected with importance sampling.

The stochastic sampling method interpolates between pure greedy prioritization and uniform random sampling. The probability of being sampled is ensured to be monotonic in a transition's priority, while guaranteeing a non-zero probability even for the lowest-priority transition. Concretely, define the probability of sampling transition i as

P(i) = (pᵢ^α)/(∑ₖ pₖ^α)

where pᵢ > 0 is the priority of transition i. The exponent α determines how much prioritization is used, with α=0 corresponding to the uniform case.

Prioritized replay introduces bias because it changes this distribution in an uncontrolled fashion, and therefore changes the solution that the estimates will converge to. We can correct this bias by using importance-sampling (IS) weights:

wᵢ = (1/N·1/(P(i)))^β

that fully compensates for the non-uniform probabilities P(i) if β= 1. These weights can be folded into the Q-learning update by using wᵢδᵢ instead of δᵢ - weighted IS rather than ordinary IS. For stability reasons, we always normalize weights by 1/maxᵢwᵢ so that they only scale the update downwards.

The two types of prioritization are proportional based, where pᵢ = |δᵢ| + ϵ and rank-based, where pᵢ = 1/(rank(i)), the latter where rank(i) is the rank of transition i when the replay memory is sorted according to |δᵢ|, For proportional based, hyperparameters used were α= 0.7, β₀ = 0.5. For the rank-based variant, hyperparameters used were α= 0.6, β₀ = 0.4.

PaperSource

In Syntology repository known, no verified implementation (declared_code; repositories: 5 listed of 77 in the graph, strongest link: mentioned on GitHub). The lookup matched 'PRIORITIZED EXPERIENCE REPLAY' ignoring case. This answer is about arXiv:1511.05952, the paper the archive credits with this method.

Code Syntology holds under other names, as the lookup lists them (code_nearby); not a complete list, and none of them is this method.

Origin paper of this answer, arXiv:1511.05952 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 80 ran (of which 62 constructed an object rather than computing a result; 72 with no instrument failure: 4 honoured, 0 violated, 68 with no contract checked; 8 where Syntology's instrument failed) · 31 unverified (of 111 harvested samples) · 43 pointer-only (licence). 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.

What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).

Papers archive 2025-07-28

archive papers tagged: 138 · with a code link: 61 · where Syntology ran a sample: 19 (17 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (19 of 138 tagged: 17 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument)

Page 1 of 2: papers 1 to 100 of 138, 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 82 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
Reinforcement Learning (RL)72
reinforcement-learning68
Reinforcement Learning60
Deep Reinforcement Learning41
Model-based Reinforcement Learning20
Atari Games17
Q-Learning17
Continuous Control15
continuous-control14
Decision Making11
Board Games8
OpenAI Gym8
Multi-agent Reinforcement Learning7
Game of Go6
MuJoCo5
Offline RL5
Starcraft5
model5
Autonomous Driving4
Atari Games 100k3

Usage over time archive 2025-07-28

Papers per year tagged with Prioritized Experience Replay: 2015 to 2025, peak 26 26 0 2015: 1 paper 2015 2016: 0 papers 2016 2017: 2 papers 2017 2018: 8 papers 2018 2019: 10 papers 2019 2020: 22 papers 2020 2021: 26 papers 2021 2022: 21 papers 2022 2023: 22 papers 2023 2024: 17 papers 2024 2025: 9 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (138 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

Replay Memory

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