4 ms·
File system allocation tables effectively are highly optimised databases already. I think the issue isn't the file system itself but rather the OS syscalls.
by laumars 7y ago
File system allocation tables effectively are highly optimised databases already. I think the issue isn't the file system itself but rather the OS syscalls.
- naasking 7y ago> File system allocation tables effectively are highly optimised databases already. I think the issue isn't the file system itself but rather the OS syscalls. It really is the file systems as well. If allocation tables are highly optimized databases, they're not the kind of safe and robust database we're used to: https://danluu.com/file-consistency/ https://danluu.com/file-consistency/
- laumars 7y ago> If allocation tables are highly optimized databases, they're not the kind of safe and robust database we're used to Those two points aren't mutually exclusive (that link, by the way, is discussing syscalls like I'd mentioned). When I talk about "optimised" I mean in terms of other limits placed on the table that makes sense with regards to storing file metadata but wouldn't be desirable for a RDBMS.