[Boris Tsipenyuk]

I have the same configuration here are some important tips:

Make sure all switch ports are set to jumbo frames (not on by default)

Make sure network interface on OS on client and server is set to jumbo frames

The rest of these worked well for me but results may vary!

On the client Mac enable the following settings (running via Sudo don’t survive reboot for testing)

sudo sysctl -w net.inet.tcp.doautorcvbuf=0
sudo sysctl -w net.inet.tcp.doautosndbuf=0
sudo sysctl -w kern.ipc.maxsockbuf=4194304
sudo sysctl -w net.inet.tcp.maxseg_unacked=32
sudo sysctl -w net.inet.tcp.delayed_ack=2
sudo sysctl -w net.inet.tcp.win_scale_factor=7
sudo sysctl -w net.inet.tcp.rfc1323=1
sudo sysctl -w net.inet.tcp.sendspace=1048576
sudo sysctl -w net.inet.tcp.recvspace=1048576

I am unclear if you are using a Mac or Windows server. What I have found on windows servers is I disabled ALL tcp offload options on the interfaces, but make sure receive side scaling is enabled.

Also if a windows server in local security policy make sure to disable samba digital signing (I’m mobile so I can’t look up exactly what this setting is called)

[Boris Tsipenyuk]

Hello all, I just got one of these am testing from a macmini6,2 running 10.9.4 – – AFP and SMB – and what I have seen
the final setup will almost certainly be different in some way (probably the file server piece)

netgear switch
Server: vsphere 5.5 server with a windows 2012 r2 virtual machine (native file share for SMB, ExtremeIP for AFP)
10 gigabit equalogic 6000 san array with 16 x 7200 RPM sata running raid 6 – I will be testing further in raid 50 and with faster drives to make sure that’s not the bottleneck

I’ve been using blackmagic design’s disk benchmark from the app store as well as AJA recommended on this thread (other suggestions welcome)

I wanted to ping this group because what’s clear in my testing is that the sysctl settings are absolute key (as long as being on 10.9 vs. 10.8)
the best results I’ve gotten are as posted by Chris Duffy Earlier in the thread)

sudo sysctl -w net.inet.tcp.doautorcvbuf=0
sudo sysctl -w net.inet.tcp.doautosndbuf=0
sudo sysctl -w ern.ipc.maxsockbuf=8388608
sudo sysctl -w net.inet.tcp.sendspace=4194304
sudo sysctl -w net.inet.tcp.recvspace=4194304
sudo sysctl -w net.inet.tcp.maxseg_unacked=32
sudo sysctl -w net.inet.tcp.delayed_ack=2
sudo sysctl -w net.inet.tcp.win_scale_factor=7

so far I have managed sustained 450 MB/Sec write and about 615 MB/Sec Read using SMB volumes via blackmagic

when using AJA I get even wackier results and generating ton of file write errors in the console log (this is for a 16 gig file test)

8/3/14 4:39:07.754 PM AJA System Test[331]: Disk write error: fd = 7, tried to write 12746752 bytes, stopped at 18446744073709551615
8/3/14 4:39:07.000 PM kernel[0]: smb2_smb_read_write_async: smb_rq_reply failed 22
8/3/14 4:39:07.756 PM AJA System Test[331]: Disk write error: fd = 7, tried to write 12746752 bytes, stopped at 18446744073709551615

8/3/14 4:39:34.668 PM AJA System Test[331]: Average read rate = 682.95
8/3/14 4:39:34.668 PM AJA System Test[331]: Average write rate = 5762.20

for an 8 gig file test:

8/3/14 4:40:40.920 PM AJA System Test[331]: Average read rate = 677.26
8/3/14 4:40:40.920 PM AJA System Test[331]: Average write rate = 5978.89

so obviously something is out of whack (and yes system buffers are disabled on aja)

and finally here are my sweep file results from aja:

128.0 703.1 3467.3
256.0 700.5 2897.4
512.0 681.5 3447.9
1024.0 693.6 3931.2
2048.0 698.0 2926.8
4096.0 671.2 3322.4
8192.0 634.0 5222.6

(and also the same disk write errors on console log)

thanks