tool · inferred from evidence
cairo.cache
Cache settings in QuestDB that only affect the HTTP API.
- QuestDB memory climbs forever when Grafana generates unique BETWEEN queries (statement cache never reused)
When dashboards hit QuestDB with ever-changing queries like `WHERE timestamp BETWEEN X AND Y` (Grafana builds a new SQL string on every refresh instead of using bind variables), memory climbed with each reload and never came back, eventuall