goerch

I'm slowly finding my way back to testing local LLMs (out of fear of price spikes). Currently positively surprised by OpenVINO. But my private benchmarks indicate not to trust edge models too much.

One question I'm asking myself is: can LLMs be bored?

both

Maybe you are unconsciously doing the right thing(TM) already? So try doing it with SQLite instead :)

Agree with your assessment of small and reliable for SQLite. Disagree with your baseline requirement. ACID is more important for me and does not contain `No crashes`.

> Search the issues of the duckdb GitHub there’s at least 110 open and closed oom (out of memory) and maybe 400 to 500 that reference “memory”.

Ah, missed this the first time around. Will check this out. And yes, I noticed that DuckDB rather aggressively tries to use the resources of your computer.

Understood: SQLite is to Postgres as DuckDB is to ClickHouse.

That sounds like a rather serious application. Did you file an issue?

Interesting: I transferred the idea of a matrix being stored row or column wise to the database world and assumed this was a more physical than theoretical feature (not a native speaker here)?

Looking forward to check out `pg_duckdb`, yes.

> For most of the data the sizes we often deal with it's perfect.

Interested here: for me it works for out of core work. Where is the limit? On a related note: do you need to handle concurrency restrictions?

Theoretically I would agree, but practically I still wonder why we need different database engines for row and columnar storage if supporting different types of indices is trivial(TM) for Postgres?

It is a educational/R&D type project. We are more of backend developers and `rill` worked fine as a rapid visualization frontend with low learning curve for us.

Edit: still realizing that I can't use markdown on HN...