SYNCTHING CPU USAGE PLUS

Limit folder concurrency to improve performance Database performance: reduce duplication Consider always running the monitor process Crash or hard shutdown can case database inconsistency, out of sync Syncing issues, database missing sequence entries lib/ignore: panic: runtime error: index out of range with length 0 panic: Should never get a deleted file as needed when we don't have it Doesn't react to Ctrl-C when run in a subshell with -no-restart (Linux)

SYNCTHING CPU USAGE PLUS

The database schema has been improved and will result in a migration plus compaction at first startup after the upgrade.

The observed behavior with -no-restart should be the same as before but the internals differ.

This facilitates crash reporting and makes logging behave more consistently. Syncthing now always runs the monitor process, which previously was disabled with -no-restart. The default is the number of available CPU threads ('GOMAXPROCS'). In addition to just limiting concurrent scans it now also limits concurrent sync operations. The config option maxConcurrentScans has been removed and replaced a new config option maxFolderConcurrency. This limits Syncthing's peak RAM usage when there are many connected devices all requesting file data. A new config option maxConcurrentIncomingRequestKiB has been added to limit the maximum amount of request data being concurrently processed due to incoming requests.

Syncthing cpu usage