Hello, 

 Also the SANHQ manual has a chapter on performance monitoring that can help explain the SANHQ charts as well. 

 Don 

Hello, 

 IOs are measured per pool or by member. 

 The experimental analysis is based on a relatively small blocksize, of 8K I believe. If you are doing large sequential reads with jumbo frames the blcoksize will be much larger. 

 The I/O rate is measured from the request time until it's acknowledged.  When you have larger blocksizes it takes longer to send that data so the response time (latency) is longer. However, the benefit is that you get greater MB/sec in those cases.   Small I/O size provide better I/O rates but less MB/sec.   It's a balancing act with all storage. 

 Also with Linux you can set the readahead value to increase MB /sec on reads. 

 Make sure that all the Linux best practices are set 

http://downloads.dell.com/solutions/storage-solution-resources/(3199-CD-L)RHEL-PSseries-Configuration.pdf

Also are you using the CNA with DCB enabled?   If you have dedicated iSCSI switches the need for DCB is diminished.  

 Generally speaking more volumes do better than single mega volumes.  In part because each volume negotiates a queue depth.  Typically values are 64 to 128.  This means on very busy volumes the queue may fill and pause additional I/O until the queue drains down. 

Regards,

Don 

Hello, 

 Well technically, he just did "g"  for 'gig"    Which most take as 10Gb interfaces.   

 Don 

 Hello, 

FYI: The 10GbE model of the 61xx series is a 6110.  The 6100 is GbE only. 

 Regards,

Don