4 ms·
First enumerate all of the constraints and guarantees your database provides. All the basic minimum services it provides for every access. Look at the memory it
by simonh 7y ago
First enumerate all of the constraints and guarantees your database provides. All the basic minimum services it provides for every access. Look at the memory it takes to provide those, and the processor utilisation overhead to perform all those checks, and services such as to guarantee ACID compliance, guarantee referential integrity, enforce a global type system, etc, etc.
Every single access of every single piece of data, for anything, will incur all of those overheads every time. There is no way to opt out or choose a different balance of guarantees or trade-offs without implementing them on top of the OS provided ones.
- twhitmore 7y agoYou're describing the fact that OS apis are typed, and check state for validity. That's already the case and OS system calls already incur those costs. In a database, preparing a query compiles the access plan (ie all the above) on the server side. There's no reason it would be any less efficient than an OS call today. Could in fact be more efficient, since you would probably be able to leverage set-based operations on the server (ie OS) side rather than iterating everything on the caller.
- simonh 7y agoIf OSes are already doing all these things, to the same degree required, and with the same overhead of a DB based OS, why do we need a DB based OS? What more is it giving us, and how is it providing that at no additional cost over the current model? 'On the server side' isn't magic. You don't get server side operations for free and these 'server side' operations would be occurring on the same computer.
- ken 7y agoEven my database doesn't incur all overheads for every operation. I don't know why an OS designed around the concept would. It's interface, not implementation.