I have an underpowered CPU (Intel Pentium processor D1508) but I still wouldn’t expect Syncthing to saturate the CPU while transferring files (it is not scanning).
I took some cpu profiles: would anyone have the time to take a peek and tell me what might be the issue here?
Well, something is going to be the limit – if it’s not the network or the I/O it’s going to be the CPU. If that CPU doesn’t offer whatever extensions are used for hardware crypto & hashing then that’s likely to be the bottleneck.
2 core 4 threads is less than what most people carry in their pockets nowadays, and phones, while still being considered “weak” devices, usually ship SHA extensions on newer CPUs.
I suspect the transfer rate will be simillar to the hashing rate reported on startup.
I didn’t realize htop hid kernel processes by default. It looks like I am hitting a performance bottleneck with my CPU but it’s not coming from Syncthing’s hashing: it’s my zfs pools encryption. This CPU is so freaking old it can’t handle writing to an encrypted filesystem. heh.
Just a small addition, I run ST on a TrueNAS Core install running on an Intel G4560 build (2C/4T)/16GB ECC RAM. It works perfectly well and rarely uses 100% - I confess I don’t encrypt files though.