don't let redis save to disk #131
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We’ve found that this line “--save 20 1” instructs redis to save all of its data to the disk every 20 seconds. It also then makes it so it loads that data at boot. If that’s changed to
--save ""it doesn’t save and it doesn’t load, it just exists in memory as long as the container is on (and a container restart is thus much faster). We’ve seen noticeable load decrease on servers especially around disk i/o with this setting off and I think it’s probably a better default.The downside is that every container restart clears the Drupal cache, so perhaps folks should understand the tradeoffs in this setting.