Skip to content

Conversation

@dwdougherty
Copy link
Collaborator

No description provided.

@dwdougherty dwdougherty requested review from a team and LiorKogan January 13, 2026 22:42
@dwdougherty dwdougherty self-assigned this Jan 13, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 13, 2026

DOC-6156

@github-actions
Copy link
Contributor


## LRM eviction {#lrm-eviction}

Starting with Redis 8.6, the Least Recently Modified (LRM) eviction mode is available. LRM is similar to LRU but only updates the timestamp on write operations, not read operations. This makes it useful for evicting keys that haven't been modified recently, regardless of how frequently they are read.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mode --> policies

- Your application has a clear distinction between read-heavy and write-heavy workloads
- You want to evict stale data that hasn't been updated, regardless of read activity

To configure the LRM mode, the following policies are available:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

avoid "mode"


This distinction makes LRM particularly useful in scenarios where:

- You want to preserve frequently read data, even if it's not being modified
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one is LRU

- `allkeys-random`: Evict keys at random.
- `volatile-lru`: Evict the least recently used keys that have the `expire` field
set to `true`.
- `volatile-lrm`: Evict the least recently modified keys that have the `expire` field
Copy link
Member

@LiorKogan LiorKogan Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix the 4 volatile policies:

instead of "that have the expire field set to true" ---> "that has an associated expiration (TTL)"

I'm not aware of any such field (and if there is - it is an internal implementation details)


To configure the LRM mode, the following policies are available:

* `volatile-lrm` Evict using LRM among the keys with an expire set.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

expire set --> associated expiration (TTL)

Copy link
Contributor

@andy-stark-redis andy-stark-redis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Language LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants