Looks interesting! Could you add a when to use / when not to use / compare with duckdb and click house section to the docs?
It's a little hard to reason about the use case for "in memory" but file based, and what the limitations are. What specific product problem did you build this to solve?
Beyond that it would be helpful to have some hardware variation in the performance claims. Does zen5 avx512 make a difference? A node with optane (memory or disk)? Threads vs clock speed? ARM vs X86? Feels like this was built with a specific cloud native deployment in mind and a certain scale and speed of storage.
It's a little hard to reason about the use case for "in memory" but file based, and what the limitations are. What specific product problem did you build this to solve?
Beyond that it would be helpful to have some hardware variation in the performance claims. Does zen5 avx512 make a difference? A node with optane (memory or disk)? Threads vs clock speed? ARM vs X86? Feels like this was built with a specific cloud native deployment in mind and a certain scale and speed of storage.