I upgraded my work laptop to 0.11.1 this morning and did the same with my aging home PC this morning. The work laptop is a Lenovo T530 so has a decent spec - Core i7, 8GB RAM, SSD. The home machine doesn’t fair so well - Core i3-2100 (yup, it’s that old), 8GB RAM, 7200rpm HDD.
The upgrade on the work laptop was pretty much unnoticeable. The upgrade has crippled the home machine - I’m guessing the rehash of all the files is grinding the CPU and HDD.
Is there any way to get some sort of progress indication of how the rehash is going?
Hmm… just looking around and I see that the old Syncthing db directory (C:\Users\A\AppData\Local\Syncthing\index) has 226 files whilst the “new index-v0.11.0.db” only has 75.
Is it fair to say the number of files in the new db folder will match the old and so I’m only about one third of the way through?
(damn, it’s been slogging away for about an hour now)
Also, if I look in the web UI, the three large shared folders (one for docs, one for music, one for RAW photos) show (eg) 19000 total files and 18999 out of sync. Is that a concern or does it just mean it’s rehashing the lot?
Maybe, I don’t know. Not necessarily, at least. It depends.
The 19000 files are the one it has rehashed so far. If you know there are 25000 files or so according to explorer, then you know how far it’s come.
It’s expected that every file is out of sync at this stage - that’ll sort itself out when the devices sync after the initial scan. The actual sync will be very fast since presumably nothing or very little needs to actually change.
Progress note: One of the three larger folders “completed initial scan” and now the computer is completely useable again and the noise from the HDD is much reduced. Perhaps having three folders being queried all at once saturated the drive.
The scan of the remaining two folders appears to be going more quickly now as well.
Maybe we should default to a single hasher per folder. The current setup is kinda optimized to maximize resource utilization when doing a single folder. If there are many, and they’re on the same disk, this is not optimal. Or maybe runtime.NumCPU() / numberOfFolders + 1.