3 ms·
There is no requirement to have the file fit in RAM to mmap it, that's the point. Obviously you'd have a file per column (or index), and use directories to rep
by mgaunard 4y ago
There is no requirement to have the file fit in RAM to mmap it, that's the point.
Obviously you'd have a file per column (or index), and use directories to represent tables.
This is the correct way of doing it and yet so few databases do it.
- mamcx 4y agoYes, I understood, but "mmap a file" that should be a database is not "easy", because now you can deal with segfaults and other weird things that are out the normal playbook. Of course, depending on the other things of the list this is or not a major issue. Is more about how combining several ideas leads to a easy or complex implementation.
- preseinger 4y ago"correct" is not an objective measure, it's a function of use case mmap is not a panacea, it improves specific access patterns by incurring specific costs, it's definitely not true that mmap is the right choice for all databases