as51340

Yes we used this number based on some of our workloads and it is definitely lower bound... As I am thinking now we should have moved this lower bound a bit up yes

Hey I am Andi, the author of blog post and wanted to jump in... First neo4j is not an in-memory db since its main storage is on disk. It does come with cache mechanisms using which data eventually ends in main memory but that is completely opposite approach of what we wanted to show in this blog post and what Memgraph is capable of doing. Memgraph is an explicite in-memory storage (or was since now it has capability to also use disk) because everything is computed in memory, no caching needed no buffer pool, for in-memory storage the only disk-related thing is securing the durability but that is different topic