So in your ifconfig output, for ix0, the interface is showing in promiscuous mode. Are you running something that's doing packet capture? Or do you have VMs configured? At least for testing purposes you might want to disable any of that stuff and get the card out of promiscuous mode. Notably, tcp segmentation offload and some other performance enhancements appear to be disabled on the interface when it's in promiscuous mode. That could be the source of some of your issues.
Also, this may be a dumb question, but you did reboot after you set all the kernel tunables, but before you tested, correct?
A few comments on the tunables:
net.inet.tcp.recvspace (and sendspace) seem small. we typically use 4194304.
Most of the zfs tunables in your list are better left at their defaults. The zfs.arc parameters are largely ignored by the most recent versions of ZFS and most of that code is self tuning and better left at the defaults. In any event, based on your hardware config, none of those ZFS tunables will make a measurable difference on your read and write speeds.
There are also Linux and BSD live CDs around.. you could always try booting one on your windows workstation to rule out(or in) Windows as the problem.
Well, windows will do smb multichannel by default as well. You need to enable that in freenas.Acquacow
Starting to think i'm stuck with what i have and i'll just have to load balance link aggregate them.
I'm running FreeNAS on a HP ProLiant DL360 G7 8-Port with 2 3.46 GHz Hex-Core Intel Xeon X5690. The full build is in my signature.
Its a server but i'll have to look into that. But i was getting full 10gig band with when i had windows on it when i was doing testing with an ASUS XG-C100C card
Promiscuous would be a side effect of the bridge.
So i tried the value you posted twice just to make sure i didn't type it wrong and both times it failed so i had to go restart it from the console its self. The message on the console that it had 0 buffer. Not really sure what it meant by that.
root@nasbench:~ # sysctl net.inet.tcp | grep space net.inet.tcp.sendspace: 2097152 net.inet.tcp.recvspace: 4194304 root@nasbench:~ #
Checked the freeBSD forum and here and everywhere else i can think of can't find anyone saying that intel maxing out at 6.5
root@nasbench:~ # dmesg | grep CPU: CPU: Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz (3700.07-MHz K8-class CPU) root@nas1:~ # iperf3 -c 192.168.1.2 Connecting to host 192.168.1.2, port 5201 [ 5] local 192.168.1.51 port 21212 connected to 192.168.1.2 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 1.05 GBytes 9.00 Gbits/sec 0 567 KBytes [ 5] 1.00-2.00 sec 1.09 GBytes 9.35 Gbits/sec 0 586 KBytes [ 5] 2.00-3.00 sec 1.09 GBytes 9.37 Gbits/sec 0 603 KBytes [ 5] 3.00-4.00 sec 1.09 GBytes 9.35 Gbits/sec 0 620 KBytes [ 5] 4.00-5.00 sec 1.09 GBytes 9.37 Gbits/sec 0 637 KBytes [ 5] 5.00-6.00 sec 1.09 GBytes 9.36 Gbits/sec 0 653 KBytes [ 5] 6.00-7.00 sec 1.09 GBytes 9.35 Gbits/sec 0 670 KBytes [ 5] 7.00-8.00 sec 1.09 GBytes 9.36 Gbits/sec 0 685 KBytes [ 5] 8.00-9.00 sec 1.09 GBytes 9.35 Gbits/sec 0 700 KBytes [ 5] 9.00-10.00 sec 1.09 GBytes 9.37 Gbits/sec 0 715 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 10.9 GBytes 9.32 Gbits/sec 0 sender [ 5] 0.00-10.00 sec 10.9 GBytes 9.32 Gbits/sec receiver iperf Done.
So your "MAX" speed statement should be qualified and not a blanket statement. Please try not to spread invalid or incomplete information. Also, I have a X5650 running at 1.6GHz that will do full 10gbe over iSCSI (1147MB/s). Interestingly enough, my 10gbe card is also a 82599ES (the same chip and driver for the x540).That's a very fast CPU though. I'm working with xeon-d and other 1.8/1.9GHz L-series xeons in my lab =)
So your "MAX" speed statement should be qualified and not a blanket statement. Please try not to spread invalid or incomplete information. Also, I have a X5650 running at 1.6GHz that will do full 10gbe over iSCSI (1147MB/s). Interestingly enough, my 10gbe card is also a 82599ES (the same chip and driver for the x540).
Triple check that the MTU is 1500 on all points, quality cables of appropriate lengths are used, and that all "tunables" are disabled and removed. If your able, check for frame/crc errors on the switch.
From there, open two ssh sessions, one for iperf, and one for top. Monitor CPU usage on BOTH ends while running iperf. If you see the CPU pegged at 1.6 or 16% (1/6th of all (6)cores at 100%), it may be limited to one core. check to see if iperf3 allow to specify the number of threads and set it to two.