Hey @U028ART884X 👋 Usual caveat: 'it depends'. Our in-memory KV store isn't massively optimised (it's pretty much just a Clojure sorted-map), on the assumption it's mostly used for non-production use-cases - you might find that a throwaway RocksDB/LMDB instance is faster if they can cache your entire database in memory. My guess (although best to measure it with real-life scenarios) would be that CPU would be the bottleneck in most cases - XT queries run lazily with a relatively small working set, so the RAM usage for each query tends to stay quite low. Regarding multi-threading - each db instance should only be used from one thread at a time. The query indices are stored in immutable data structures (in the in-memory KV stores), which, once you've taken a snapshot (using db) means multi-threaded access is cheap. (In Rocks and LMDB this uses their MVCC snapshots, so a similar principle applies) Hope this helps, and let us know if you have further questions 🙂 Would you mind mirroring/if I mirrored this question onto http://discuss.xtdb.com so that others can find it in search engines?

https://discuss.xtdb.com/t/general-query-performance-what-should-i-expect-from-in-memory-db/73