Performance

Solid Accounting is built for files into the millions of transactions. If yours feels slow, work through these.

Large file is slow on open

Opens are slow when the WAL file is large. Force a checkpoint:

  1. Close the file (File → Close).
  2. Reopen it. The first open after a close runs a WAL checkpoint that consolidates pending writes into the main DB.

If still slow, the file may have grown via many short transactions. Run File → Compact — it does a full VACUUM. Takes a few minutes on multi-GB files; do this overnight on a backup first if you're nervous.

Reports take forever

Reports re-aggregate from journal entries every time. Big date ranges on big files are expensive. Mitigations:

  • Use the fiscal-year filter instead of "all time" when possible
  • Run reports in Simple mode (Settings → Mode) — fewer columns
  • Custom reports with multiple grouping dimensions are the slowest; check Pro tier features → custom-report templates which cache

Search is laggy

Search uses a SQLite FTS5 index that's rebuilt on demand. If the index is out of date (e.g., after a bulk import), force a rebuild:

File → Diagnostics → Rebuild search index

Takes ~30 seconds per 100k transactions.

App memory keeps growing

Open a single file at a time. Solid Accounting can keep multiple files open via window switching, but each holds a SQLite handle and PDF cache. Close files you're not actively using.

If memory still grows over hours of use, that's a leak — please email support with:

  • File size on disk
  • How long the app was running
  • Approximate memory at start vs end
  • macOS: Activity Monitor → Solid Accounting → Memory screenshot
  • Windows: Task Manager → Details → solidaccounting.exe → Working set
  • Linux: ps -o rss= -p $(pidof solidaccounting) output

"Cloud Backup taking too long"

First backup of a large file is slow because every block has to be encrypted, hashed, and uploaded. Subsequent backups are content- addressed: only changed blocks transfer.

Typical first backup: ~10 MB/sec on a residential connection. Typical incremental backup: under 30 seconds for a few thousand new transactions.

If first-backup throughput is dramatically lower, your ISP may be throttling — try a wired connection or a different network. Backup runs in the background; the app stays responsive.

Updated May 2, 2026
Edit this page on GitHub →
Was this helpful?

We use this to prioritize which docs to improve. No tracking, no email follow-up.