Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No persistence #179

Merged
merged 5 commits into from
Oct 10, 2024
Merged

No persistence #179

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
476efa2
No persistence
melroy89 Oct 9, 2024
6ed07e2
Mention the --save CLI argument
melroy89 Oct 9, 2024
441533b
Update persistence.md
melroy89 Oct 9, 2024
6521d54
Update topics/persistence.md
melroy89 Oct 10, 2024
3b8d64b
Update topics/persistence.md
melroy89 Oct 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions topics/persistence.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,17 @@ dataset to disk every 60 seconds if at least 1000 keys changed:

This strategy is known as _snapshotting_.

## No persistence

If you prefer **not** to have persistence (eg. when using a Valkey instance solely as a cache) that is also possibility.
melroy89 marked this conversation as resolved.
Show resolved Hide resolved

First comment out or remove all existing `save` lines that are present in the current configuration file.
Then add the following configuration instead:
melroy89 marked this conversation as resolved.
Show resolved Hide resolved

save ""

Alternatively, you can also use the `--save ""` argument on the `valkey-server` binary.

### How it works

Whenever Valkey needs to dump the dataset to disk, this is what happens:
Expand Down