convore.json/groups/epio/future-plans-for-redis-support/messages.json

[{"user_id": 8740, "stars": [], "topic_id": 40860, "date_created": 1309457681.0393281, "message": "@leafstorm Yes, we've had problems with Virtual Memory support when we used Redis as part of our core infrastructure", "group_id": 2873, "id": 1530398}, {"user_id": 34637, "stars": [], "topic_id": 40860, "date_created": 1309457904.108192, "message": "Will you charge by RAM usage just on databases, on Web sites, or on everything?", "group_id": 2873, "id": 1530437}, {"user_id": 34637, "stars": [], "topic_id": 40860, "date_created": 1309457446.272022, "message": "Hey, ep.io people. First, I would like to say that I am really glad that you support Redis. However, as of 2.4, diskstore is gone, and Virtual Memory has huge warning signs that say, \"WARNING. DON'T USE THIS, IT'S NOT THAT GREAT.\" Considering that there is not likely to be bigger-than-RAM data support until post-Redis 3.0, how is that going to affect your Redis support?", "group_id": 2873, "id": 1530364}, {"user_id": 8740, "stars": [], "topic_id": 40860, "date_created": 1309457723.3492661, "message": "since we're changing to charging by RAM usage, we don't have many issues selling RAM-only instances of redis (with a little bit of swap in there too)", "group_id": 2873, "id": 1530403}, {"user_id": 8740, "stars": [], "topic_id": 40860, "date_created": 1309465285.052026, "message": "@leafstorm Everything; we're going to announce the new pricing soon, but websites, databases, search servers, etc., will all be charged on the same three metrics (memory, disk usage, and bandwidth)", "group_id": 2873, "id": 1532197}]