You want the illusion that your database is entirely in memory, just as want the illusion that all your memory is in your L1 cache.
What does that mean?
And what kind of actual memory usage should people expect with a "big" database?
Datomic is designed for data sets larger than memory, and also to do a good job caching working sets that do fit in memory.
Of course. But you didn't answer my question.
Let's say someone has an application with 100GB of data in Datomic.
What kind of memory usage should he expect for the "peer" process?
See also https://docs.datomic.com/cloud/operation/caching.html.
I don't want illusions. When it comes to databases I want simple and predictable.
The data is modeled as a collection of (entity,property,values,txn) tuples (with schema on property). They are stored in a log and a few ordered sets (indexes) that are structured somewhat like 2-layer btrees with large pages. These pages and the tail of the log are loaded as needed while running queries. The nature of the data model also gets you point in time queries and queries across time (e.g. all previous values of a property).
(Which is natural if you consider the retarded development of disk/ram vs processing power; cf the memes of "disk is the new tape" "ram is the new disk")
I'm not sure I follow - are you saying it is desired to have an entire database also in memory? You don't probably mean that, but I thought a key feature of databases is for them to be your offline storage so things don't need to be in memory. I wouldn't be able to fit the contents of my SQL databases into memory on any machine I own.