Is it possible to set the config in the newer version so it will work as close to the old version (say v1.76.2 previously suggested) as possible?
Maybe with?
--maximum-concurrent-segments=1 --maximum-concurrent-pieces=1
I’m now running v1.90.2 with reduced --maximum-concurrent-segments=5 --maximum-concurrent-pieces=100 (defaults are 10 and 300 respectively). And the -p 4 -t 4 - have always been there.
uplink cp -p 4 -t 4 --maximum-concurrent-segments=5 --maximum-concurrent-pieces=100 --progress=false
So far it is running, let’s see if it’ll be better:
root-node-1 | 14.8GiB 0:04:25 [67.3MiB/s] [57.3MiB/s] [> ] 0% ETA 18:38:18
root-node-1 | 15.2GiB 0:04:30 [71.9MiB/s] [57.6MiB/s] [> ] 0% ETA 18:32:56
root-node-1 | 15.5GiB 0:04:35 [64.4MiB/s] [57.7MiB/s] [> ] 0% ETA 18:30:27
root-node-1 | 15.8GiB 0:04:40 [59.4MiB/s] [57.7MiB/s] [> ] 0% ETA 18:29:51
root-node-1 | 16.0GiB 0:04:58 [11.4MiB/s] [54.9MiB/s] [> ] 0% ETA 19:26:13
root-node-1 | 16.0GiB 0:04:58 [11.4MiB/s] [54.9MiB/s] [> ] 0% ETA 19:26:12
root-node-1 | 16.3GiB 0:05:03 [69.2MiB/s] [55.1MiB/s] [> ] 0% ETA 19:21:03
root-node-1 | 16.7GiB 0:05:08 [65.6MiB/s] [55.3MiB/s] [> ] 0% ETA 19:17:30
The MikroTik router through which the traffic is going from the qemu/kvm VM => Proxmox => MikroTik => WAN is barely loaded as you can see 
