Performance issues?

[nema69]

Hey everyone,
recently I've been noticing some performance issues when using Trilium.
They manifest in delay when opening notes, slow interface rebuilding when changing window size and even some slight delay when typing.
For reference I'm on version 0.96 atm and using Ubuntu on a Thinkpad with a i7-8650u and 16 GB of RAM, so not the newest hardware, but nothing ancient either.
Is anyone else experiencing this?
Do you have any tips how I could diagnose this further?
Thanks for your input :)

[eliandoran]

It should be fixed (at least partially) in the version that will be released in ~30 minutes.
Check it out and let me know if you still have issues.

[dosubot[bot]]

Hi @nema69! I'm Dosu and I’m helping the Trilium team.

There are known performance issues in Trilium 0.96 that match what you're seeing—delays when opening notes, UI lag when resizing, and typing lag. These are often linked to how CKEditor is managed (it gets destroyed and recreated when switching note types, which isn't optimized) and to large or complex notes, especially those with deep template inheritance or heavy use of Mermaid diagrams. Mermaid rendering, in particular, can block the UI if diagrams are large or use the ELK layout engine, causing the app to become unresponsive for a while [source][source].

To diagnose further:

• Check backend logs (log subdirectory in your Trilium data directory, or via the app menu: Advanced → Show backend log) and frontend logs (CTRL-SHIFT-I or Advanced → Open Dev Tools) for slow operations or errors [source].
• Use the /api/metrics endpoint to see instance stats (note count, DB size, etc.)—large databases or notes can slow things down [source].
• Try simplifying template inheritance, splitting up very large notes, or temporarily disabling sync to see if that helps [source].
• If you use Mermaid diagrams, try breaking them up or avoiding the ELK layout engine [source].
• Restarting the app or reloading the frontend (CTRL-R) can sometimes clear up UI issues [source].
• You can also start Trilium in safe mode (TRILIUM_SAFE_MODE=true ./trilium) to rule out custom scripts as a cause [source].

If you want to dig deeper, standard Linux/Electron profiling tools (like Chrome DevTools' Performance tab) can help pinpoint bottlenecks, since Trilium doesn't have built-in client-side profiling.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}