[Edwards Willeam]

Hi Irrani,

Have you tried nic porting? What I mean is using multiple network
ports in parallel to increase the link speed beyond the limits of any
port.
Also please try below steps.
LSI MegaRAID performance tuning; controller policy for RAID-1 vs
RAID-5
Performance of various RAID levels
What is the relative performance of the different RAID levels?
Symptom
Not sure what settings to use with the different RAID levels
available
Fact
Variable environments, Intel, AMD platforms
Fix
LSI Logic MegaRAID controllers are designed to provide the best
performance throughput. They support a number of policies:
* Write policy – Write Through (WT) and Write Back (WB)
* Read policy – Read Ahead (RA), No Read Ahead (NRA) — also called
normal, and Adaptive Read Ahead (ARA)
* Cache policy -Direct I/O (DIO) and Cached I/O (CIO)
The following are the 12 ways that LSI Logic MegaRAID controllers can
be configured:
WB, NRA, DIO WB, RA, DIO WB, ARA, DIO
WB, NRA, CIO WB, RA, CIO WB, ARA, CIO
WT, NRA, DIO WT, RA, DIO WT, ARA, DIO
WT, NRA, CIO WT, RA, CIO WT, ARA, CIO
Write Policy
*
Write-Through Cache In Write-through caching, the controller sends a
data transfer completion signal to the host when the disk subsystem
has received all the data in a transaction. This caching strategy is
considered more secure, since a power failure will be less likely to
cause loss of data. The default setting is Write-Through.
*
Write-Back Cache In Write-back caching, the controller sends a data
transfer completion signal to the host when the controller cache has
received all the data in a transaction. Because the magnetic media is
slower than the cache, write-back caching allows the operating system
to move on to other tasks more quickly, improving overall system
performance. In write-back cache, data is written to the disk when it
is forced out of controller cache memory or forced out by the flush
timer. An optional battery backup can be used to protect data in the
cache against data loss as a result of a power failure or system
crash.
Read Policy
* Read-ahead Read-Ahead capability allows the adapter to sequentially
read ahead of requested data and store the additional data in cache
memory, anticipating that the data will be needed soon.
* No-Read-Ahead Only the requested data is read and the controller
does not read ahead.
* Adaptive specifies that the controller begins using read-ahead if
the two most recent disk accesses occurred in sequential sectors. If
all read requests are random, the algorithm reverts to No-Read-Ahead;
however, all requests are still evaluated for possible sequential
operation..
Cache Policy
*
* Cached I/O Cached I/O option specifies that all reads and writes
are
buffered in cache memory. Data is transferred to cache and the host
concurrently. If the same data block is read again, it comes from
cache memory.
Direct I/O Direct I/O specifies that reads and writes are not
buffered
in cache memory. Direct I/O does not override the read policy
settings.
Recommended Settings for the best Performance:
*
For RAID 0: Write Through, No Read Ahead (Normal), Direct I/O
*
For RAID 1: Write Through, No Read Ahead (Normal), Direct I/O
*
For RAID 5: Write Back, No Read Ahead (Normal), Direct I/O
Note
The information provided here is intended to assist you in finding
the
optimum settings for your application of the product. The settings
that works best for you may not always be the same in different
environments

Regds,
Dufrence