You’re right, you can use logseq without a db. Nice!
There is a version that uses SQLite which is what I was using, it seems like that’s required for certain features like db graphs, so a bit of a bummer:
app start time from 20s to 1 ~ 2s
feat/db: loads 784571 datoms in 20077 ms
this PR: restore-graph! loads 2880 datoms in 945 ms
open "All pages" from 4s to 400ms
open "#movies" from 5s to 400ms
cmdk search && node reference are much faster, 3~4s to less than 100ms
table view scrolling now maintains a minimum frame rate of >40 fps. Previously (in feat/db), such large table views were nearly unusable, with frequent frame drops to 1 fps during scrolling.
add/remove object from "#movies" are much faster
You’re right, you can use logseq without a db. Nice!
There is a version that uses SQLite which is what I was using, it seems like that’s required for certain features like db graphs, so a bit of a bummer:
https://github.com/logseq/logseq?tab=readme-ov-file#-database-version
But database version’s performance is great
Result compared to feat/db:
https://github.com/logseq/logseq/pull/11774
performance isn’t really my main concern with DB.