Hello there ![]()
I have the same problem on long pages (few hundred lines/bullet points, sometimes a thousand and more; my graph is hundreds of pages large) both on my workstation and my laptop (even without the battery-saving mode).
It’s due to the lag input: I press enter and then tab and start to write, but the program is slow to catch up, so the cursor is set back at the start of the line after some letters have already been written. Sometimes characters even end up at the wrong line, or bullet points are in the wrong order.
The fact that the document is loaded on the fly is also a big problem for long pages, it requires scrolling down the whole document in order to then be able to quickly jump here and there through it (including with the CTRL+F search functionality), and sadly also make switching between pages a bit of a pain.
For me those performance issues are a big deal, it makes using LogSeq unenjoyable, and almost unusable in some context.
I’ve got a bit of hope for those matters regarding the upcoming DB version, but meanwhile I’m considering looking for another note-taking app.
(I’m new to the forum but the performance issue with long pages seem to be known for some time? Related: https://discuss.logseq.com/t/logseq-unusable-for-long-form-pages/21256/.)