Hi folks, see ^above - I just published a new v1 patch release with a couple of changes 🙂
Do we have any documentation related to the new kv-cache module?
Hey @namit.shah not yet, but I can write more about it if you're keen to try it out. I added an example of how to use it in your config: https://github.com/xtdb/xtdb/commit/6c77f7c7f76b933820636918f41731737e1aeecc#diff-d401e3768ffc5f231a60321f1dc699182abe0da0aa02b1df0463973f90e357f3R126-R136
The idea is to improve performance of pull or entity calls during very large queries (where an in-memory cache isn't very suited) and the document store latencies are high
Sure. I will try configuring it and update you on the outcome. If I am facing any issues while configuring, will let you know.
Thanks. Hopefully there's also a small performance boost from the RocksDB upgrade - keen to hear how you get on :)
Might be a silly question but what is the difference between the block cache that we can configure in the RocksDB and this new kv-cache? Does both of them serve the same purpose or it is something else?
Block cache is a lower level concept, and interestingly it can be shared across otherwise independent RocksDB instances (in the same process). It accelerates basic KV operations. This doc cache is specifically about accelerating entity and pull queries, and now is able to use RocksDB to dramatically increase the size of the cache
No such thing as a silly question :)