"I trust Redis-on-disk every day less." --Salvatore

Re:"I trust Redis-on-disk every day less." --Salvatore by antirez on Wednesday June 01, 2011 @03:41AM (#2606409)

Redis is an in memory but persistent on disk data store. So memory is used to serve data, but disk is used in order to persist. This is the Redis model since the start. What I was questioning in the linked group message is to go for disk not just for persistence but also to take ready-to-serve organized data.

Actually in the persistence side we plan to do more work to make Redis better, for instance Redis 2.4 that is entering release candidate can save/load most databases on disk ten times faster.

In the future we plan to explore a new AOF format that is more compact and faster to process, and the ability to rewrite the log without a background process (BGREWRITEAOF).

[ Parent | on HN ]

Re:"I trust Redis-on-disk every day less." --Salvatore by antihero on Wednesday June 01, 2011 @07:59AM (#2606882)

Is there anything we have to do to make sure redis stores our data persistently? cron for BGSAVE? Or is it generally handled fairly well already?

[ Parent | on HN ]

Re:"I trust Redis-on-disk every day less." --Salvatore by antirez on Wednesday June 01, 2011 @08:06AM (#2606892)

BGSAVE in cron is not needed, you can configure Redis (and this is the default config) to automatically save every N seconds if there are at least M changes in the dataset. It is possible to configure multiple save points. More info: http://redis.io/topics/persistence

[ Parent | on HN ]

Re:"I trust Redis-on-disk every day less." --Salvatore by xpaulbettsx on Thursday June 02, 2011 @10:49PM (#2614966)

That makes way more sense, thanks!

[ Parent | on HN ]