:memory: vs file-based DuckDB for low-traffic cost trade-off
Reducing cost for a low-traffic analytical workload in DuckDB requires a choice between an in-memory database using ":memory:" and a persistent file. The in-memory option removes disk I/O and storage cost and can lower read latency, but data is lost on process exit and size is bounded by available RAM. A persistent file provides durability across restarts an