I have used Logseq since January 2024 and it has been great so far. I have had some performance issues, though. I am making a post instead of a bug report, because it is a collection of different things going on.
I have tried it on 3 different laptops. I used a Thinkpad X1 Carbon gen 6, and I thought maybe the processor was too old, since Logseq lagged a lot. The lag was very noticeable when battery saving mode was enabled. I’ve switched to a System76 Darter Pro 8 which should have a better battery, and I’ve found that the battery is draining pretty quickly, and since I’ve been using Logseq this whole time, I didn’t think that maybe Logseq is one of the battery drainers.
I recently got an M2 Macbook Pro for work and went to a conference 2 days ago. I saw how ARM-based macs have a really good battery life and I tried using it one workday without plugging it in at all and it lasted the 8 hours. This was mostly using Chrome and several Electron-based apps such as Slack.
I went to a conference that was about 7 and a half hours. I was actively taking notes during all of the talks, and the battery was draining pretty quickly, with less than 30% halfway through. I tried turning battery saver mode on, and even though the Mac has a powerful and efficient processor, I suffered from the same lag as the Thinkpad. As the battery was reaching a critical state, I decided to just finish taking notes with vim, and the battery lasted much longer, and there was no lag.
It seems also that as your notes grow, the more performance suffers, it might even be quadratic in performance. There are other bugs, such as when battery-saving mode is on, if you type “Hello”, you might end up typing “elloH” or “lloHe”.
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.
Hello,
At first thanks for the good work, logseq is a very cool and abolutely useful piece of sofware. I use it daily, for work and home and it is now an essential part of my setting.
I can confirm the issue, at least on windows.
Since last version, I tried on two different laptops, one dell one hp and I clearly detected that logsqeq, even with not so long pages, eats the battery at a very accelerating rate (like 35% of the whole battery in 40 minutes).
