Mirfster
Doesn't know what he's talking about
- Joined
- Oct 2, 2015
- Messages
- 3,215
So, I am doing some similar testing as JoeSchmuck (and others) with running FreeNas 9.10 as a VM on ESXi 6.0 U2. Things are pretty smooth and I have a lot more testing/tweaking to do before I would even consider this "Production Ready".
Anyways, I decided to see what network speeds I could obtain between the FreeNas VM and a SME Server VM (based on Cent OS).
Keep in mind that on both VMs
It would appear to me that vSphere/ESXi 6.0 is limiting the actual speed... I wonder if this is due to it being the free version? Perhaps someone who owns the full version can elaborate on this.
I may try out some testing with using the "E1000" NIC; but feel that it would not really make a difference.
Edit: I am also thinking that it may be the actual CPU bottle-necking VMXNet3. VM Host is currently running Dual Xeon Hex Core L5639 @ 2.13 GHz. CPU is set to "High" for FreeNas. Might swap them out for X5650 CPUs @ 2.67GHx to see if that makes any difference but not 100% sure...
Anyways, I decided to see what network speeds I could obtain between the FreeNas VM and a SME Server VM (based on Cent OS).
Keep in mind that on both VMs
- I am using the VMXNet3 Emulated NICs
- Latest VMTools have been installed
- FreeNas is using the updated kernel driver as opposed to the one built into 9.10
- MTU has not been changed from the defaults
- Main HW is not changed on the VMs (with the exception of an actual 10GB - More on this later)
- The two ports of the 10GB NIC are connected to each other with a Cisco SFP-H10GB-CU3M 3 Meter Twinax 10GB Cable
- Freenas is running as the IPerf Server and SME is connecting
- Example: iperf -p 5001 -c %DesiredNIC% -t 30 -w 512k
- Simply leverages the Intel 1GB NICs on the MB
- Results: Not too shabby for a 1GB NIC since it is showing 2.22 Gbits/sec
- Code:
------------------------------------------------------------ Client connecting to 10.20.10.14, TCP port 5001 TCP window size: 244 KByte (WARNING: requested 512 KByte) ------------------------------------------------------------ [ 3] local 10.20.10.23 port 40595 connected with 10.20.10.14 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-30.0 sec 7.74 GBytes 2.22 Gbits/sec
- Created a vSwitch that has an Intel 10GB Dual Port NIC
- Intel 82599EB
- PCIe v2.0 (5.0GT/s)
- Added a NIC to each of the VMs as a VMXNet3 on vSwitch1
- Set Static IPs, ensuring they were on a different Subnet
- Results: Were basically the same as Test Case #1
- Code:
------------------------------------------------------------ Client connecting to 11.50.0.3, TCP port 5001 TCP window size: 244 KByte (WARNING: requested 512 KByte) ------------------------------------------------------------ [ 3] local 11.50.0.4 port 47986 connected with 11.50.0.3 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-30.0 sec 7.92 GBytes 2.27 Gbits/sec
- Deleted the vSwitch I created in Test Case #2
- Deleted the NICs I create on the VMs from Test Case #2
- In VMWare, I passed one of the Intel 10GB Port to each VM
- FreeNas got #0 and SME got #1
- Set Static IPs, ensuring they were on a different Subnet
- Results: At least twice what I received from the previous tests
- Code:
------------------------------------------------------------ Client connecting to 11.50.1.2, TCP port 5001 TCP window size: 244 KByte (WARNING: requested 512 KByte) ------------------------------------------------------------ [ 3] local 11.50.1.3 port 36900 connected with 11.50.1.2 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-30.0 sec 16.7 GBytes 4.79 Gbits/sec
It would appear to me that vSphere/ESXi 6.0 is limiting the actual speed... I wonder if this is due to it being the free version? Perhaps someone who owns the full version can elaborate on this.
I may try out some testing with using the "E1000" NIC; but feel that it would not really make a difference.
Edit: I am also thinking that it may be the actual CPU bottle-necking VMXNet3. VM Host is currently running Dual Xeon Hex Core L5639 @ 2.13 GHz. CPU is set to "High" for FreeNas. Might swap them out for X5650 CPUs @ 2.67GHx to see if that makes any difference but not 100% sure...
Last edited: