Sometimes I post some feature requests while I am using Logseq because since version 0.2.x Logseq solved many problems about performance. And I thought it would go better with performance in future.
As I decided to migrate to Logseq, I wrote about 1000+ pages, some page has about more than 1000+ nodes. And it turns out performing much worse. I will point out 3 things in my case below :
- When pages arrive about 1000+ page ,it searches very slow. its gragh is slow too(which I dont very care)
- When nodes in page arrive about 1000 or more ,it took much time to open a page, while opening, I have to wait for the whole app and worry whether it will be not responding. I see the effort that developer has made, to split page in to some part and just show one part of page until I click previous or next. But it is not enough, whether in performance or intereaction.
- When I tagged many nodes also about 1000+,I use query to list them.It took much time for me to wait when I just switch every field to show or hide.
such things it can be perform well in some other software just like notion,obsidian,wolai.I chose Logseq cause I can own my own data. I wonder there is some relation between performance and user-stored data.
This is my advice and what I undergoing while use.