Hi there – I have a large local graph on my Windows 11 desktop, & lately the initial loading time (meaning, the time between the app starting up & un-freezing to be used) has gone up to around ten minutes. The same graph works fine on Android, & when loaded into demo.logseq.com. Any ideas?
Win 11 is updated, & I just downloaded the latest v of logseq from logseq.com. Grateful for any ideas!!
Thanks!
Same here, on a Windows 11 and 10, too.
Aha. For me, the problem turned out to be that I was using (Google) DriveSync. Even though there was a local version of the graph on my laptop, for some reason … logseq was treating the graph folder differently than a non-DriveSync-linked folder. Everything’s working much more quickly, now.
@Penguinita Do you mean that if your local files are in a sync GDrive folder, that makes the initial load slower?
Yes, exactly.
Unfortunately, I still can’t get logseq’s native sync feature to work correctly, so I’m in search of a better solution…
I’d like to hear if there’s someone else with the same scenario.
I had exactly the same issue…I wanted to use Logseq on two different machines, so put my graph folder on Google Drive, and this slowed down my start up immediately to 4 minutes! And I have a graph of about 2,500 files. So I moved the graph to a local folder, and the start up time dropped to less than 20 seconds…still a bit long, but way better than what it was…
Please email support@logseq.com and we’ll help you get things sorted with Logseq Sync.
Almost every case of slow startup and responsiveness of Logseq can be traced back to storing a graph in a shared folder (especially when that folder is shared by file sync tools like iCloud, Dropbox, Google Drive, etc.).
20 seconds is still a lot. Unless you’re on very old hardware, startup should be less than a handful of seconds. How often do you re-index and do you notice a speed difference after you do?