In the read-only case, pretty much any embedded DB with a large userspace cache configured won't read data back in redundantly.
In the specific case of LMDB, this is further extended since read transactions are managed entirely in shared memory (no system calls or locks required), and the cache just happens to be the OS page cache.
Per a post a few weeks back, the complete size of the HN dataset is well under 10GB, it comfortably fits in RAM.
In the specific case of LMDB, this is further extended since read transactions are managed entirely in shared memory (no system calls or locks required), and the cache just happens to be the OS page cache.
Per a post a few weeks back, the complete size of the HN dataset is well under 10GB, it comfortably fits in RAM.