Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can configure redis to flush to disk on write operations though you lose on performance.


That is not comparable to writes completing after they are flushed to disk.


>appendfsync always: fsync every time new commands are appended to the AOF. Very very slow, very safe. Note that the commands are appended to the AOF after a batch of commands from multiple clients or a pipeline are executed, so it means a single write and a single fsync (before sending the replies).

https://redis.io/docs/management/persistence/

It's very slow, but if you really want to wait for fsync before replying, it can do that.


I was unaware they could make that guarantee.

Thanks for the correction.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: