News for hackers. Stuff that matters.
Re:Redis: the AK-47 of databases by adamtj on Friday January 28, 2011 @11:53AM (#2152517)
"The entire dataset is in RAM."

How can they guarantee that, when RAM is little more than a disk cache on modern operating systems? Is there a syscall that prevents specified pages of virtual memory from being paged out to disk? Or is Redis implemented as a kernel module?

Re:Redis: the AK-47 of databases by antirez on Friday January 28, 2011 @12:09PM (#2152586)
Redis uses a memory layout that, unless the instance is completely idle, will make it very easy to touch every page even if there are just a few queries per second.

So fare in two years we never saw an instance where there was a latency problem because part of the dataset was swapped on disk by the OS. This is why we currently don't use mlockall().

Re:Redis: the AK-47 of databases by wingo on Friday January 28, 2011 @11:59AM (#2152541)
Your swap should be off, and there is mlockall(2).

The kernel does let userspace have a /little/ fun on its own.