Syncthing DB Migration Errors?

Jaxel · September 2, 2025, 12:39pm

Linuxserver updated their Syncthing recently, and this morning Watchtower installed it on my Synology. It looks like this new version requires a database migration… and that has been running on my system for several hours. However, in the logs, which seem to be updating around every 15 minutes, it shows a lot of errors:

2025/09/02 08:36:09	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 08:36:08	stdout	2025-09-02 08:36:08 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 08:36:03	stdout	2025-09-02 08:36:03 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 08:36:02	stdout	2025-09-02 08:36:02 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): out of memory (7)" log.pkg=main)
2025/09/02 08:26:13	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 08:26:12	stdout	2025-09-02 08:26:12 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 08:26:07	stdout	2025-09-02 08:26:07 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 08:26:06	stdout	2025-09-02 08:26:06 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): out of memory (7)" log.pkg=main)
2025/09/02 08:13:59	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 08:13:58	stdout	2025-09-02 08:13:58 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 08:13:53	stdout	2025-09-02 08:13:53 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 08:13:52	stdout	2025-09-02 08:13:52 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 07:56:01	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 07:56:00	stdout	2025-09-02 07:56:00 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 07:55:55	stdout	2025-09-02 07:55:55 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 07:55:54	stdout	2025-09-02 07:55:54 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 07:41:57	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 07:41:56	stdout	2025-09-02 07:41:56 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 07:41:51	stdout	2025-09-02 07:41:51 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 07:41:51	stdout	2025-09-02 07:41:51 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): out of memory (7)" log.pkg=main)
2025/09/02 07:30:10	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 07:30:09	stdout	2025-09-02 07:30:09 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 07:30:04	stdout	2025-09-02 07:30:04 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 07:30:02	stdout	2025-09-02 07:30:02 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 07:14:46	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 07:14:45	stdout	2025-09-02 07:14:45 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 07:14:40	stdout	2025-09-02 07:14:40 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 07:14:39	stdout	2025-09-02 07:14:39 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): out of memory (7)" log.pkg=main)
2025/09/02 07:03:23	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 07:03:22	stdout	2025-09-02 07:03:22 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 07:03:17	stdout	2025-09-02 07:03:17 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 07:03:14	stdout	2025-09-02 07:03:14 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 06:46:30	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 06:46:29	stdout	2025-09-02 06:46:29 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 06:46:24	stdout	2025-09-02 06:46:24 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 06:46:23	stdout	2025-09-02 06:46:23 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 06:28:53	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 06:28:52	stdout	2025-09-02 06:28:52 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 06:28:47	stdout	2025-09-02 06:28:47 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 06:28:45	stdout	2025-09-02 06:28:45 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 06:11:28	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 06:11:27	stdout	2025-09-02 06:11:27 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 06:11:22	stdout	2025-09-02 06:11:22 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 06:11:19	stdout	2025-09-02 06:11:19 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 05:54:55	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 05:54:54	stdout	2025-09-02 05:54:54 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 05:54:49	stdout	2025-09-02 05:54:49 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 05:54:48	stdout	2025-09-02 05:54:48 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 05:39:18	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 05:39:17	stdout	2025-09-02 05:39:17 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 05:39:12	stdout	2025-09-02 05:39:12 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 05:39:11	stdout	2025-09-02 05:39:11 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 05:22:57	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 05:22:56	stdout	2025-09-02 05:22:56 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 05:22:51	stdout	2025-09-02 05:22:51 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 05:22:50	stdout	2025-09-02 05:22:50 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 05:03:11	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 05:03:10	stdout	2025-09-02 05:03:10 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 05:03:05	stdout	2025-09-02 05:03:05 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 05:03:02	stdout	2025-09-02 05:03:02 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 04:50:02	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 04:50:01	stdout	2025-09-02 04:50:01 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 04:49:56	stdout	2025-09-02 04:49:56 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 04:49:55	stdout	2025-09-02 04:49:55 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): out of memory (7)" log.pkg=main)
2025/09/02 04:38:56	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 04:38:55	stdout	2025-09-02 04:38:55 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 04:38:50	stdout	2025-09-02 04:38:50 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 04:38:49	stdout	2025-09-02 04:38:49 ERR Error opening database (error="open: startfolderdatabases: getfolderdb: openbase: vacuumandoptimize (VACUUM;): disk I/O error (5386)" log.pkg=main)
2025/09/02 04:11:25	stdout	[ls.io-init] done.
2025/09/02 04:11:25	stderr	Connection to localhost (127.0.0.1) 8384 port [tcp/*] succeeded!
2025/09/02 04:11:24	stdout	2025-09-02 04:11:24 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)
2025/09/02 04:11:20	stdout	2025-09-02 04:11:20 INF Applying database migration (path=folder.0001-saxr6ven.db script=04-alter-blocks-tables.sql log.pkg=db/sqlite)
2025/09/02 04:11:19	stdout	2025-09-02 04:11:19 INF syncthing v2.0.4 "Hafnium Hornet" (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2025/09/02 04:11:19	stdout	[custom-init] No custom files found, skipping...
2025/09/02 04:11:19	stdout	    
2025/09/02 04:11:19	stdout	───────────────────────────────────────
2025/09/02 04:11:19	stdout	Build-date: 2025-09-02T06:15:45+00:00
2025/09/02 04:11:19	stdout	Linuxserver.io version: v2.0.4-ls194
2025/09/02 04:11:19	stdout	───────────────────────────────────────
2025/09/02 04:11:19	stdout	User GID:    100
2025/09/02 04:11:19	stdout	User UID:    1031
2025/09/02 04:11:19	stdout	
2025/09/02 04:11:19	stdout	───────────────────────────────────────
2025/09/02 04:11:19	stdout	GID/UID
2025/09/02 04:11:19	stdout	───────────────────────────────────────
2025/09/02 04:11:19	stdout	
2025/09/02 04:11:19	stdout	https://www.linuxserver.io/donate/
2025/09/02 04:11:19	stdout	To support LSIO projects visit:
2025/09/02 04:11:19	stdout	
2025/09/02 04:11:19	stdout	───────────────────────────────────────
2025/09/02 04:11:19	stdout	   Brought to you by linuxserver.io
2025/09/02 04:11:19	stdout	
2025/09/02 04:11:19	stdout	      ╚══════╝╚══════╝╚═╝ ╚═════╝
2025/09/02 04:11:19	stdout	      ███████╗███████║██║╚██████╔╝
2025/09/02 04:11:19	stdout	      ██║     ╚════██║██║██║   ██║
2025/09/02 04:11:19	stdout	      ██║     ███████╗██║██║   ██║
2025/09/02 04:11:19	stdout	      ██║     ██╔════╝██║██╔═══██╗
2025/09/02 04:11:19	stdout	      ██╗     ███████╗██╗ ██████╗
2025/09/02 04:11:19	stdout	
2025/09/02 04:11:19	stdout	───────────────────────────────────────
2025/09/02 04:11:18	stdout	[migrations] no migrations found
2025/09/02 04:11:18	stdout	[migrations] started

Should I be worried? I don’t see any progress information on the migration, so I don’t know if it’s continuing through the errors.

calmh · September 2, 2025, 1:26pm

It will not continue through them, sorry.

domlang1995 · September 2, 2025, 6:17pm

I have the same error messages after updating my Syncthing docker container on Unraid.

FordPrefect · September 2, 2025, 9:56pm

Similar error in my logs - Linuxserver.io docker image in UnRaid after installing 2.0.5 this afternoon.

Linuxserver.io version: v2.0.5-ls194 Build-date: 2025-09-02T20:10:38+00:00

2025-09-02 17:47:28 ERR Error opening database (error=“open: startfolderdatabases: getfolderdb: openbase: runscripts (INSERT INTO blocklists_v4 (blocklist_hash, blprotobuf)\nSELECT blocklist_hash, blprotobuf FROM blocklists ORDER BY blocklist_hash): out of memory (7)” log.pkg=main)

rramstad · September 3, 2025, 12:12am

Yep, another Unraid person, in my situation, my server is thrashing so hard I can’t log into it or do anything with it. Samba shares are not working. When I use a saved URL to peek at the Syncthing console, I see only this:

2025-09-02 16:57:48 INF syncthing v2.0.4 “Hafnium Hornet” (go1.24.6 linux-amd64) root@buildkitsandbox 2025-09-02 06:17:46 UTC [modernc-sqlite, noupgrade] (log.pkg=main) 2025-09-02 16:57:53 INF Starting temporary GUI/API during migration (address=0.0.0.0:8384 log.pkg=main)

I’ve tried letting it run for hours, never seems to complete, and instead it seems to restart periodically i.e. if I revisit that page, I’ll see the same messages but with a later timestamp.

When I was able to get into the Unraid console – once – I was able to turn off all other Docker containers and all VMs – I was thinking it might help the system finish more quickly.

I’m a bit worried, TBH.

tomasz86 · September 3, 2025, 12:45am

Just a comment, but your build of Syncthing hasn’t been compiled with the standard/C version of SQLite. Normally, this may not matter that much, but you’re speaking about poor performance here, and from my testing, modernc-sqlite is about 20% slower. I’ve now also noticed that the same is true for the build used by the topic creator.

If possible, you may want to try contacting whoever maintains those builds and ask them to compile Syncthing using the C version of SQLite instead.

rramstad · September 3, 2025, 12:49am

Fascinating. I’m using the Syncthing docker provided through the Unraid forums via linuxserver.io

I have no connection with them at all and at the moment my server is so totally borked that I can’t even manipulate Docker, so the performance gain is, shall we say, academic right now.

That said, good catch, and certainly someone should suggest this change to the linuxserver.io folks.

Yep, from my end, and it’s super annoying, my server had no problems going from 1.x to 2.0. For whatever reason, going from 2.0.2 or 2.0.3 to 2.0.4 is resulting in massive out of memory problems and thrashing.

tomasz86 · September 3, 2025, 12:53am

There are some additional migrations in the latest versions, plus VACUUM of the database after they are complete, and some users have been reporting excessive resource usage or even crashes in the process.

Personally, I haven’t experienced any performance issues (even on very low-end hardware), but my systems are mostly desktop PCs and possibly Android, and most of the reported issues seem to be concentrated around NAS-like systems.

rramstad · September 3, 2025, 12:57am

Yep. I’m seeing classic *nix resource starvation when trying to get Syncthing running on the new version. It provides an indication that it’s doing a migration, then basically everything stops working, including the GUI, Samba shares, you name it.

When I drill down into what is going on, top indicates that all my CPU is being eaten by the swap process. When I look at Syncthing, all indications point to the migration being started over and over again, presumably due to lack of memory.

tomasz86 · September 3, 2025, 1:06am

Hmm, I’m wondering if there is any difference in memory usage during the upgrade (and VACUUM) between our standard C build and modernc-sqlite. I may try to do some testing later this week, as before, I only checked the CPU and how long it took to hash a completely new folder (and there, the difference was about 20%).

rramstad · September 3, 2025, 1:18am

Yeah, it would be interesting to know.

The timing on all this is quite unfortunate. Unraid sends out reminders to folks on the 1st of the month to do upgrades / updates.

Anyone like me who saw the 2.0 upgrade on the mirror system would be caught in the same situation… I updated Unraid to 2.0.1 fairly recently, and then was auto prompted to update because of it being the 1st. I think the system tried to get me to 2.0.3 but that failed, I’ve subsequently managed to update the Docker… that log from earlier was 2.0.4 but I think right at this instant I can get to 2.0.5.

I’ve lost most of the day due to this and the server being down is really difficult, as it’s super reliable, this is my first major downtime in several years.

Anyhoo, I will probably update the container, go into the filesystem and see if I can manually delete old 2.0.x migrations that presumably are incomplete or failed, and try starting the container with nothing else running.

Getting into the server is a chore and takes quite some time as Unraid doesn’t like messy startups – in fact, the latest Syncthing attempts ended up corrupting the USB boot key, and also forcing a parity check across all drives which will take more than a day to complete…

rramstad · September 3, 2025, 1:25am

Nothing in the filesystem for the failed migrations.

The migration from 1.0 to 2.0 took a while but succeeded. That said, I’m hesitant to delete the current 2.0 database just to force another migration.

I’m going to let the server settle – rebuild parity for 26+ hours and hope that someone comes up with a solution for the Docker image at some point. Syncthing is necessary for my configuration, but it’s not the end of the world if it doesn’t run for a couple of days.

(Conversely, I can’t have the server down again.)

rramstad · September 3, 2025, 1:57am

I attempted to file a bug as a way to encourage the use of the better standard SQLite but the linuxserver bug report page requires things I cannot provide because of the state of my system.

bt90 · September 3, 2025, 5:13am

github.com/linuxserver/docker-syncthing

[FEAT] Build with CGO

opened 05:12AM - 03 Sep 25 UTC

bt90

enhancement

### Is this a new feature request? - [x] I have searched the existing issues #…## Wanted change Syncthing v2 should be built as a static binary using CGO. ### Reason for change Syncthing v2 uses SQLite as its database backend. While the build without CGO is functional, the resulting binary is approximately 20% slower. The CGO built is also the version primarily shipped by the upstream project, which reduces the likelihood of users encountering edge cases or SQLite library related bugs. ### Proposed code change https://github.com/syncthing/syncthing/blob/6e9ccf7211aec68df5f15e4a4cceb6315b5d4c63/.github/workflows/build-syncthing.yaml#L314

It’s not strictly a bug so I created a feature request

calmh · September 3, 2025, 6:44am

Yeah, it’s pretty memory intensive for the schema migration, modernc more so than native. I ran a few perf tests and created a couple of very primitive plots. This is a test setup with one fairly large folder; 20 358 files, 14 455 737 blocks.

This is initial migration (i.e., 1.x to 2.0) using either stock 2.0.5 or 2.0.5 compiled without CGO, time on the X axis (seconds) and maximum resident set size in bytes on the Y axis. The native C version finished in about half the time compared to the modernc version and used slightly less memory, ~400 vs ~450 MB.

Then I just edited the schema version back from 4 to 3 so the migration would run and restarted. The migration takes roughly the same amount of time for both versions, but the modernc variant has almost twice the peak memory usage, 3.9 GB vs 2.1 GB. Both results are higher than I’d expected/hoped, for sure.

I tried a third variant where I removed our cache size setting and order by in the migration query (blue line), but this made quite little difference. That was with the modernc variant because it’s easier to cross build, but I expect the results would be similar for the native version.

Finally I disabled just the VACUUM, and the result is slightly hard to see in the plot below but it’s the orange line that ends before the final rise in memory usage, at about 1.7 GB. So the second, larger, memory usage peak is all for the vacuum…

Finally I realised I didn’t properly remove our temp_store = MEMORY setting, and doing that brings the modernc variant down to below 450 MB:

I think that should be the shipped default, if we think it matters for performance we’d need to add it back as a tunable…

calmh · September 3, 2025, 7:15am

github.com/syncthing/syncthing

fix(db): remove temp_store = MEMORY pragmas

main ← calmh:notempstore

opened 07:15AM - 03 Sep 25 UTC

calmh

+0 -8

This reduces database migration memory usage in my test scenario from 3.8 GB to …440 MB. In principle I don't think we're causing many temp tables to be generated anyway in normal usage, but if we do and someone can benchmark a performance difference, we can add a tunable. I ran the database benchmark before and after and didn't see a difference above the noise level.

calmh · September 3, 2025, 7:40am

Here’s the corresponding change with the 2.0.6 native-C build, peak usage 168 MiB vs 2.1 GiB.

calmh · September 3, 2025, 9:17am

On another note, is there an actual driver for using the linuxserver.io container, like it does something nice that ours doesn’t? It always seemed to me like it just added a layer of unnecessary startup tooling and questionable compilation etc choices

andycarlberg · September 3, 2025, 3:26pm

Most Unraid users (including myself) will pull template docker configs from Unraid’s app repository. There’s a linuxserver.io version there but not an official version. So a lot of Unraid users will be on that one. There’s also another one from another popular image builder. I’m not sure what it takes to publish an official one or if the Syncthing team would be interested in that.

calmh · September 3, 2025, 3:50pm

Not at all interested in doing NAS templates, just curious about why the ones that do choose the linuxserver container over a more OEM one from us.