Painfully slow data transfer on VM - 6.1

[Redtoast]

Hi,

I have just setup Proxmox 6.1 - Latest build and have installed Xpenology 6.2. Everything is working fine, apart from the network speed is VERY Slow ( 65KB/s -> 1.5MB/s ) where it should be at least 30-50MB/s.

My VM Settings are below



I have made some changes as per the forum to the MTU on both PVE node NIC and virtual and they are both set to 9000 from 1500, but if anything it's a bit slower. The traffic goes via net1, I just added net2 to test.

I ran a test with iperf3 running the server on the Xpenology end (Docker ) and the client on the PVE Node.

----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------
Accepted connection from 172.17.0.1, port 40387
[ 5] local 172.17.0.2 port 5201 connected to 172.17.0.1 port 40388
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 286 MBytes 2.40 Gbits/sec
[ 5] 1.00-2.00 sec 307 MBytes 2.57 Gbits/sec
[ 5] 2.00-3.00 sec 301 MBytes 2.53 Gbits/sec
[ 5] 3.00-4.00 sec 300 MBytes 2.52 Gbits/sec
[ 5] 4.00-5.00 sec 327 MBytes 2.75 Gbits/sec
[ 5] 5.00-6.00 sec 291 MBytes 2.44 Gbits/sec
[ 5] 6.00-7.00 sec 294 MBytes 2.47 Gbits/sec
[ 5] 7.00-8.00 sec 291 MBytes 2.44 Gbits/sec
[ 5] 8.00-9.00 sec 304 MBytes 2.55 Gbits/sec
[ 5] 9.00-10.00 sec 297 MBytes 2.49 Gbits/sec
[ 5] 10.00-10.04 sec 11.6 MBytes 2.62 Gbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 5] 0.00-10.04 sec 2.94 GBytes 2.52 Gbits/sec 73 sender
[ 5] 0.00-10.04 sec 2.94 GBytes 2.52 Gbits/sec receiver
-----------------------------------------------------------
Server listening on 5201

The otherway around server on PVE node and client from Xpenology (docker)

Connecting to host 192.168.197.11, port 5201
[ 4] local 172.17.0.2 port 50705 connected to 192.168.197.11 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 171 MBytes 1.44 Gbits/sec 90 361 KBytes
[ 4] 1.00-2.00 sec 159 MBytes 1.33 Gbits/sec 0 396 KBytes
[ 4] 2.00-3.00 sec 170 MBytes 1.43 Gbits/sec 0 404 KBytes
[ 4] 3.00-4.01 sec 170 MBytes 1.42 Gbits/sec 0 404 KBytes
[ 4] 4.01-5.00 sec 165 MBytes 1.39 Gbits/sec 0 404 KBytes
[ 4] 5.00-6.00 sec 172 MBytes 1.45 Gbits/sec 0 404 KBytes
[ 4] 6.00-7.00 sec 170 MBytes 1.43 Gbits/sec 0 404 KBytes
[ 4] 7.00-8.00 sec 175 MBytes 1.47 Gbits/sec 0 404 KBytes
[ 4] 8.00-9.00 sec 166 MBytes 1.40 Gbits/sec 0 423 KBytes
[ 4] 9.00-10.00 sec 165 MBytes 1.38 Gbits/sec 0 423 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 1.64 GBytes 1.41 Gbits/sec 90 sender
[ 4] 0.00-10.00 sec 1.64 GBytes 1.41 Gbits/sec receiver

iperf Done.

If i check "top" i can see there isn't any CPU wait. So i don't think Disk IO is the issue.

%Cpu(s): 0.7 us, 0.3 sy, 0.0 ni, 96.6 id, 2.4 wa, 0.0 hi, 0.0 si, 0.0 st

being new to all this, i not sure if this is a simple solution but if there is anyone willing to help it would be greatly appreciated.

Cheers.

 

[wolfgang]

Hi,

the e1000 vNIC is only for legacy systems and does not perform well.
Use virtio instead.

 

[Redtoast]

Hi,

the e1000 vNIC is only for legacy systems and does not perform well.
Use virtio instead.

I was afraid someone might say this. Unfortunately Xpenology is without a driver mod for VIRTIO, so I guess i'm stuck with E1000. Any opportunity for tweaking?

 

[wolfgang]

e1000 is an emulated vNIC and it is slow.
Maybe you can replace the kernel.
DSM is a normal Linux so it should be capable to run with a self-build kernel with virtio support.

Or use a NAS distribution what is build Hardware independent setups and virtualizations.
Like FreeNAS or OMV.

[1] https://www.freenas.org/
[2] https://www.openmediavault.org/