-
Notifications
You must be signed in to change notification settings - Fork 289
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.
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
fsync just once a second is a very bad idea. #3
Comments
Thanks for mentioning this. I agree that some more clarification can be made around this topic. I also look forward to providing optional fsync policies of Salvatore Sanfilippo talks about the same thing. http://redis.io/topics/persistence#how-durable-is-the-append-only-file |
I updated the README and added a |
Redis is awful database to learn from. Just keep it in mind. It did almost all wrong internally. Single thing it did well is user API. You may batch and pipeline fsync requests:
Combining batching with pipelining you may reach acceptable throughput without sacrificing durability. Of course, it will not as fast as fsyncing once a second, and it will have large latency. |
Very helpful information. Thank you for sharing with me. I'm starting to lean towards setting the sync policy to Always by default. Then the user can choose what's best for their application, even turning it off altogether. |
You should at least mention in a README, that user can loose whole second of changes.
The text was updated successfully, but these errors were encountered: