Is it time to kill the database and replace it with a LLM optimized compiled version that simply implements the required API directly in (Rust) code, without any dynamic overhead? It probably will still be based of off a base design or a base file format.
Ultimately this system will encompass the whole OS, of course, but the DB might be the best place to start.
I have seen this happening already at two different companies. And I'm also doing it as well. Particularly for search indexes where there's no risk of data loss.
There'd be no benefit. They're good general purpose databases but for any specific workload you can do significantly better on your own. For search in particular even if you use Postgres you wouldn't want to use Postgres FTS you'd want to at least use Tiger Data's extension.
childintime · · focus · HN ↗
Ultimately this system will encompass the whole OS, of course, but the DB might be the best place to start.
eatonphil · · focus · HN ↗
childintime · · focus · HN ↗
Data loss is the obvious concern. Are you perhaps reusing parts of sqlite or postgres?
eatonphil · · focus · HN ↗