Hello,
We have the same problem. It's seems that the ovirt-imageio-proxy is the bottleneck
for our setup. We use vprotect to backup a VM via api
We ask for support with vprotect team and we are currently tunning some parameters on the
kernel.
We have full 10G network in ou setup.
Here is the kernel parameter that we set. Did you manage to progress on the speed process
?
# Maximum receive socket buffer size
net.core.rmem_max = 134217728
# Maximum send socket buffer size
net.core.wmem_max = 134217728
# Minimum, initial and max TCP Receive buffer size in Bytes
net.ipv4.tcp_rmem = 4096 87380 134217728
# Minimum, initial and max buffer space allocated
net.ipv4.tcp_wmem = 4096 65536 134217728
# Maximum number of packets queued on the input side
net.core.netdev_max_backlog = 300000
# Auto tuning
net.ipv4.tcp_moderate_rcvbuf =1
# Don't cache ssthresh from previous connection
net.ipv4.tcp_no_metrics_save = 1
# The Hamilton TCP (HighSpeed-TCP) algorithm is a packet loss based congestion control and
is more aggressive pushing up to max bandwidth (total BDP) and favors hosts with lower TTL
/ VARTTL.
net.ipv4.tcp_congestion_control=htcp
# If you are using jumbo frames set this to avoid MTU black holes.
net.ipv4.tcp_mtu_probing = 1