Performance: GUI startup takes over 3 seconds

Search first

• I searched and no similar issues were found

What Happened?

Logseq takes 3 seconds to start with an empty graph on a highend system. On weaker systems probably longer (https://github.com/logseq/db-test/issues/952#issuecomment-4764050878). I don't know how much better it runs on modern architectures like Apple M5, but few people have it.

It would be great to have a native application that starts quickly to take notes of random thoughts.

Demo: https://www.youtube.com/watch?v=asFbVfMpr8o

Reproduce the Bug

1. Start Logseq

Expected Behavior

Fast application for note-taking

Screenshots

No response

Files

Raw data:

3.150 seconds (empty graph with only built-in data and 1 empty journal)
3.333 seconds (tiny graph with 3 pages and 2 additional tags)
3.250 seconds (tiny graph)
3.467 seconds (big graph. imported from OG, local)
3.450 seconds (another big graph, imported from OG, synced)

Browser, Desktop or Mobile Platform Information

NixOS 25.11.10684.8fd9daa3db09
Logseq-linux-x86_64-2.0.1-alpha+nightly.20260622

Additional Context

Hardware

PC from 2019:

• Intel i9-9900K processor at 3.6 GHz (5GHz boost)
• G.Skill Ripjaws 64 GB DDR4 RAM (3200 MHz)
• Sata SSD

Method

1. I created a screen recording with 60FPS of logseq starting with an empty new graph
2. Then measured the time between program start (1 frame before the cursor jumps to next line in terminal where logseq is started) and finished rendering of GUI with LosslesCut

I did this several times with different graphs.

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

No source files, tests, or entry points are named. Start by reproducing the measured startup timings on the listed NixOS setup with empty and sample graphs, then profile the GUI startup path. Done means identifying the startup bottleneck and demonstrating a materially faster launch with comparable measurements.