April 2015 Summaries

Redis is partnering with Database Month, a New York City-based festival for NoSQL, NewSQL, and big data technologies. During the event, they will host a Tech Talk titled "Using Redis to Create a Blazing Fast Mobile App," featuring Lukas Sliwka, VP of Engineering at Grindr. The talk will focus on how Grindr used Redis to overcome performance challenges in their mobile app, which is used by millions of people worldwide. The event will take place on April 21st at 557 Broadway, New York, NY.

Redis is an in-memory database that requires RAM to operate, with Operational RAM used for tasks and User Data RAM used for data storage. The operational RAM footprint of Redis is influenced by various deployment factors, including server type and configuration. A baseline estimate can be obtained by examining the memory footprint of a typical Redis instance on a virtualized Ubuntu 64-bit server, which is approximately 7.6MB. However, this figure may not always be accurate due to variations in results from different methods. The user data RAM consumption depends on the type and length of data stored, with longer or larger key-value pairs requiring more RAM. Redis uses various encoding schemes, such as sds (Simple Dynamic Strings) for strings, which adds overhead but also brings power and ease of use. The amount of RAM needed by Redis is still largely unanswered, but factors such as data type, length, and encoding can be considered to estimate memory consumption.