FFS "pauses" during "Compare" and during "Synchronize"

[2SS Capt]

The happens on 2 different computers, one Windows 10 laptop (i5, 256 GB SSD) and one Windows 11 laptop (i7, 1TB SSD), both running FFS 14.2 syncing to a Windows 10 Desktop (i7 with 1TB SSDs)

During "Compare" it may scan through 8000-14000 files and then "pauses" for 15-25 seconds, then resumes, may scan another 2,000 or another 5,000+, it always seems to be different but eventually finishes...

During "Synchronize" it will start transferring and randomly the transfer rate will drop to 0 MB/sec and sit there for 20+ seconds then resume for a bit and stall again, it does eventually finish but it takes probably 5-6 times longer to finish than if it would just run non-stop as it should... It doesn't happen every time (about 80% of the time it does "stall"), on a rare occasion it is quick and finishes as it should.

Also, the "initially searching for folders" most of the time takes over 15 seconds on a local 1 GB/sec network... This is a home network that is operating well below capacity...

[xCSxXenon]

Sounds like a failing destination, whether it be connection, software, are hardware failure

[2SS Capt]

Here is a picture of a recent transfer, as you can see the green has many flat spots where it paused, I did the same sync last night and it ran completely non-stop.

[2SS Capt]

Anyone have any ideas on this, just started happening since I upgraded to FFS 14.0 (currently on 14.2)

[2SS Capt]

Ok, I'm starting to think it is my network/router... About the same time I replaced my old router with a TP-Link Deco system... Internet works great but FFS seems to hang... I rebooted the network and it transferred perfectly (I had it set to auto-reboot once a week, I changed it to every day). We'll see what happened...

[2SS Capt]

FFS was working good for a couple days, not back to the pausing... Any ideas? Disk cache issue? The pauses are alway almost exactly 20 seconds, the run times vary... Very frustrating... Happens wired or wirelessly...

[kriebie]

Destination SSD overheating perhaps? Try monitoring it with CrystalDiskInfo.