![]() ![]() I have implemented this for the next version so that stats progress gradually rather than in bursts. ![]() ![]() With FFS's task-based architecture this interleaving doesn't happen naturally, *but* it can be introduced without loss of performance by a careful sequencing when inserting work items to the queue. while listing each folder item, it is directly analyzed before continuing with the next). On the Apple Macbook everything starts and runs with a similar. analysis of these items (file, folder, symlink) + update of the UI stats.Ī naive folder traversal automatically does some interleaving (e.g. This behavior isn't deliberate, but an artifact of the new FFS 10 multithreaded folder traversal which divides the work into multiple steps, simplified: 1. This then leads to a sudden "surge" of new items that are found, when in reality FFS is just analyzing the data it has "buffered". ![]() The corresponding "analysis steps" that update the stats as shown on the GUI are queued to the back of the workload. Hope this Your observation is correct! The apparent "hangs" are in fact situations where FFS is busy traversing lots of directories one after another. I had to stop using FFS then for the MAC and resorted to Synology's Drive,that works fine, but then the architecture is different - its a client -server rather a external HDD model. It would then continue for up 20 minutes or more. On using FFS 10.4, this slow down got worse, the scanning would simply stop, sometimes for several seconds at a time, and always at different files. Keep versions of deleted/updated files Prevent disc space bottlenecks via optimal sync sequence Full Unicode support Highly optimized runtime performance Include/exclude files via filter FreeFileSync portable and local installation available Handle daylight saving time changes on FAT/FAT32 Use macros time, date, etc. 450Mbit/s, but scanning (not transfer) was still an issue. that restored file transfer speeds to being comparable to Windows speeds e.g. However All Mac versions of FFS I used showed an issue of scanning rapidly (with Windows like speed) up to circa 52k files, then it would dramatically slow down and continue, completing its cycle of circa 80k files in about 6 minutes. 330k files are scanned in circa 65 seconds. To be more specific, This is about FFS on a Mac and syncing with data on a Synology NAS. no bad hard drive sectors) and that there is no. Transfer speed to the NAS from with both computers is always about 450 MBit/s.Īny idea what FreeFile Sync is doing on the Macbook that causes it to slow down so much ?Īny idea what I can do to change the settings either on the Macbook or NAS ? Instead, I put my trust in the program and I make sure that my computer hardware is running smoothly (i.e. The NAS is setup for SMB, I heard that Apple deprecated AFP, so I turned it off in the NAS. But it works, the scanning is just incredibly slow. However after circa 52k files, the scanning ' pauses' sometimes for several seconds then runs in stages usually at about 30 or 30 files a second for several minutes. On the Apple Macbook everything starts and runs with a similar performance to the Windows machine. Transfer of files runs at about 450Mbit/s. Performance of FreeFileSync on Windows is perfect, circa 320k files are scanned on the NAS at several 1000 files per second. I'm not saying "go back to QTS 4.5.4" or so, but it's just that I can't reproduce your exact setup with AFP & QTS 5.x here at my end.The system involves a Windows 10 PC, MacBook and a Synology NAS. (and, for more than one single reason, no intention to move to 5.x any time soon) and Macs with QNAP via SMB, and it's as fast as it can be, all other unrelated limitations considered. (Big Sur can still mount AFP-shared volumes.) macOS Sierra though Catalina “fails silently” in this method, letting you turn on AFP in the Sharing preference pane’s File Sharing section, even if there are no volumes that AFP can share. In Big Sur, Apple dropped the ability to share volumes via AFP entirely, but even though Catalina retained AFP-sharing support, as noted above, APFS-formatted volumes could not be shared over AFP. Way back in OS X 10.9 Mavericks, Apple began moving away from AFP in favor of the industry-standard SMB, although it still hasn’t removed support. As with most older protocols, it got long in the tooth, and Apple went from just supporting the Windows and Linux world’s SMB to shifting to it as the only built-in sharing method. AFP dates to the pre-OS X days, with a version appearing in System 6 in the late 1980s. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |