Equallogic - W2K8 latency with IO larger than 64KB
Hello,
I was wondering if anybody at all has experienced an issue like this. EQL firmware tested was 5.2.2 and now 5.2.4 I have tried with both a physical and virtual machine with the same results.
Client Windows 7 64bit
Server - W2K* standard R2
EQL PS6100XV
Whenever copying a large file such as an DVD iso file I experience around 100ms latency wand the queue jumps to 30-40. IO size is 128kb in SANHQ. Throughput is around 100MB/s
If I set the Max io disk size under ESX to 64kb from the default of 32MB it is basically 0 latency with the same throughput.
I have been searching around where to set this setting with W2K8. Is this to be expected with W2k8 and the latency. I guess SMB2 will send larger IO sizes and is this overwhelming the EQL?
As far as I know the Array can handle the SMB2 I/O traffic and keep up. Typically we see the bottle neck on the Host, NIC/HBA or switch (drivers, cache, settings, etc.)
I don’t know of any way to change the Max IO disk size in Windows either, not sure if that is even an option in the OS or if it would be a NIC feature.
You can check or try the following:
Switches and NIC’s - enable flow control; Switches = receive on, NIC’s Send = on (or transmit enabled)
You can also try:
netsh int tcp show global
(Take a screen shot or copy for reference to reset back if needed)
netsh interface tcp set global autotuning=disabled
To verify that it is dsabled:
netsh interface tcp show global
To set back to the default Windows behavior:
netsh interface tcp set global autotuning=normal
netsh interface tcp set global chimney = disable
To set it back:
netsh int tcp set global chimney=enabled (to set enabled mode)
netsh int tcp set global chimney=automatic to set automatic mode (available only in Windows Server 2008 R2 and Windows 7)
Hi have tried those suggestions. It is going throough a pair of stacked Force10 S25n´s from a DL2200 with 24 gb or ran and 8 cores. Single gigabit iscsi connection. I had to set the diskmaxiosize in ESX to 64kb or our latencies would go through the roof on large se quential writes. The equallogic seems to struggle a bit with anything over 64kb io. 2003 and linux are fine. Is the latency that we are seeing to be expected?
Thanks Joe. The nic is a Broadcom BCM5716c with the latest driver. The S25N switches are at firmware 8.3.2.0. The switch ports are configured like this. T ried it again and still getting the latency.
Thanks Joe. I will check out those documents. My situation must be unique, I assume that nobody else is getting these type of latencies with a W2K8 file transfer.
Thanks Don. There are 3 iscsi connection fromthe ESX server with mem 1.10 working. Ive just been looking everywhere to find some comparable stats ont he file copy between a windows 7 and 2008 r2 machine and the associated latencies to compare it against. Now generally we do have many large sequential writes so it would probably not be an issue. Esx is throwing off some latency warding for those data stores when the transfer is happening.
Joe S586
9 Technologist
•
729 Posts
1862
0
Posted June 21st, 2012 12:00
As far as I know the Array can handle the SMB2 I/O traffic and keep up. Typically we see the bottle neck on the Host, NIC/HBA or switch (drivers, cache, settings, etc.)
I don’t know of any way to change the Max IO disk size in Windows either, not sure if that is even an option in the OS or if it would be a NIC feature.
You can check or try the following:
Switches and NIC’s - enable flow control; Switches = receive on, NIC’s Send = on (or transmit enabled)
You can also try:
netsh int tcp show global
(Take a screen shot or copy for reference to reset back if needed)
netsh interface tcp set global autotuning=disabled
To verify that it is dsabled:
netsh interface tcp show global
To set back to the default Windows behavior:
netsh interface tcp set global autotuning=normal
netsh interface tcp set global chimney = disable
To set it back:
netsh int tcp set global chimney=enabled (to set enabled mode)
netsh int tcp set global chimney=automatic to set automatic mode (available only in Windows Server 2008 R2 and Windows 7)
or
netsh int tcp set global chimney=default
Also not sure if you took a look at this link:
www.speedguide.net/.../windows-7-vista-2008-tweaks-2574
Disable Jumbo (at least on your NIC) and then add it back in once you are satisfied the performance is where it should be.
-joe