Originally posted by: Sumanth.Sharma
I would like to disagree.
The I/O performance is determined by the ability of the Storage Array, the efficiency of the SAN fabric and the speed and quality of the HBA driver.
On the AIX front the Native MPIO driver/ or any other Multipathing software only lets you choose the active path(s) and load balancing features.
Since you need 500gb capacity, you may want to have say 5 100GB luns and add it to a Volume manager locally, however the size of a single lun may not be significant since you would be exposing them as logical volumes to the application right ?
The one AIX thing here is that, say with a strorage processor/controller with 512 queues and a LUN with Queue depth of 32 would mean that on the Target initiator or HBA, 1 HBA can suuport IO for upto 512/32 = 16 LUN i/o on single hba beyond which QFULL error will occur.
Typically this QFULL is gracefully handled but If am correct in Aix typically after the 3rd QFULL error, it is treated as an I/O error.
Since you need 500gb, even if you have 1LUN size as 32GB , if you have 2 HBA on the machine you can safely present 32LUNS (32GB) upto 1024GB i.e 1TB to that host so even with a ypical combination you would be fine.
Am not an expert on the Storage array front so you would be well advised to look at the performance graphs of your Array (ds4700) in your product documentation and follow the recommendations.
But apart from the QFULL error caveat (i.e. after 3 QFULL errors Aix treats as I/O error) the actual effective I/O performance is determined by your Array and SAN fabric.
#AIX-Forum