Extreme slowdown on Apple M2 Pro

Get help for specific problems

od_bo

Hi there,

I've been using FFS Donation Edition for years to back up to a private cloud and it's always been amazing. However, since I bought a new Apple MBP with an M2 Pro chip, I've noticed a huge slowdown in scanning: we're talking 1 1/2 hours as opposed to 6 to 8 minutes before. I don't understand why it has changed so drastically as the number of files hasn't changed much (±80 000). I've searched the forum but can't find an answer for M2. Can you help me?
User avatar
Posts: 4867
Joined: 11 Jun 2019

xCSxXenon

Environment/setup?

od_bo

FFS 12.4 ARM64 Donation Edition
MacBook Pro macOS Ventura 13.4.1 (22F82) with Apple M2 Pro chip

Is that what you meant?
User avatar
Posts: 4867
Joined: 11 Jun 2019

xCSxXenon

What are you syncing from/to?

od_bo

I'm syncing two different folders, one on my device, the other in my pCloud virtual drive. I've using this configuration for years, never had an issue until I changed my laptop.
Posts: 1202
Joined: 8 May 2006

therube

Just a couple older "slows".
(I'm not familiar with Mac so no clue what "M2" is or how that may or may not matter.)

viewtopic.php?t=9706
viewtopic.php?t=5729

od_bo

Hi therube,

Thanks for these threads. I've already read them and unfortunately it didn't help. The "M2" refers to the latest processor in the MacBook, which replaces the Apple M1 (which replaced the Intel processors). I don't know if it matters or not, but it's one of the main changes between the two setups.

I've done some tests in the meantime and found that FFS works fine when scaning/synchronising 2 local folders or 1 local folder with 1 folder on the virtual drive. The slowdown occurs when I scan/synchronise 1 local folder with 1 encrypted folder on the virtual drive. This could be caused by the decryption/encryption process, but it hasn't happened before.

I've contacted the cloud provider and asked for their opinion, maybe it will help.
User avatar
Posts: 4867
Joined: 11 Jun 2019

xCSxXenon

Could be that the device is simply not that fast at de/encrypting. Or, the program isn't designed for ARM yet, and has to run in the translation layer, losing performance