Varun Manjunath
07/17/2026, 6:43 PMSimran(OpenObserve)
07/20/2026, 9:51 AMZO_MEMORY_CACHE_MAX_SIZE caches parquet files on demand as queries touch them. If your 1-week query's working set is under 4GB, usage stays below the cap. It doesn't preload.
• ZO_MEMORY_CACHE_DATAFUSION_MAX_SIZE is used only while a query is actively running, so it drops back down at idle. You'd only see it near the ceiling under heavy/concurrent load.
• If this is a multi-querier setup, each node only caches its own slice, so per-pod usage will naturally be lower than the full configured size.