Comment by winrid
4 days ago
So basically if you have queries that are hard on the query planner, that constant fan out has higher CPU cost than the alternatives.
4 days ago
So basically if you have queries that are hard on the query planner, that constant fan out has higher CPU cost than the alternatives.
Taking a look at their LogQL language, I don't see anything that would be particularly hard on the planner. You can't get the fan-out that makes fully relational query planning so difficult with the kind of boolean filters they seem to use. Planning should mostly be a matter of sorting by column cardinality and query optimization so you aren't doing unnecessary operations.