3 ms·
Because when you specify a disk, you realise he's guiding you in the direction of a specific answer. Use the filesystem. It's what it's there for, particularly
by madaxe 16y ago
Because when you specify a disk, you realise he's guiding you in the direction of a specific answer.
Use the filesystem. It's what it's there for, particularly if the data never changes. Nice big cache, xfs, nested hierarchical datastore using folders based on keynames, 20 lines of code, job done. 5000 lookups a second is trivial throughput for a decent disk with a decent readahead cache.
- defen 16y agoI don't know of any hard drives that can do a seek+read in 0.2 milliseconds. Keep in mind that the reads are distributed randomly - you're almost certainly going to need more than one disk if you have less than a terabyte of RAM for your datastore.