2 ms·
My 10,000 foot high understanding is that the kind of performance you're seeking is achieved by the dark arts of database tuning. At a certain level of abstract
by brudgers 10y ago
My 10,000 foot high understanding is that the kind of performance you're seeking is achieved by the dark arts of database tuning. At a certain level of abstraction one might think about the query planner's default mode as context free and your goal as adding context sensitivity to it.
At the other end of the abstraction tree, it might be that a relational database is the wrong tool or that a row-based relational database is less right than a column based database. If you can see how the data ought to be organized for performance, then it might make sense to build project specific data structures. Or use an in-memory database. There are lots of options besides relational databases.
Good luck.
- ThePhysicist 10y agoYes I agree with what you say, sometimes it's just inconvenient to manipulate a query planner using a high-level language instead of using a more direct approach. Also, while many databases provide a way to work with underlying representations of their data, it is still quite difficult or impossible to build something entirely new (I.e. a new application) with them.
- brudgers 10y agoBecause I don't have details below the level of database and query, I had to imagine them up to write an answer. It seems like your use case is a bit unique.