I've been messing with that system, and here's the batch file I made to do the test (in the same directory as SQLIO.exe):
Code:
ECHO off

set /a mynumber=10
FOR /L %%G IN (1,1,5) DO CALL :in_fora
ECHO Done...
GOTO :eof

:in_fora
set /a myblock=1
ECHO d:\testfile.dat 1 0x0 %mynumber%>mypar.txt

FOR /L %%H IN (1,1,5) DO CALL :in_forb
set /a mynumber=%mynumber%*4
GOTO :eof

:in_forb
set /a myblock=%myblock%*4
set /a myout=1
FOR /L %%I IN (1,1,5) DO CALL :in_forc
GOTO :eof

:in_forc

sqlio.exe -kW -s20 -frandom -o%myout% -b%myblock% -BH -LS -Fmypar.txt|find /i "IOs/sec">>sqlresult.txt

ping -n 2 127.0.0.1>nul

set /a myout=%myout%*4
GOTO :eof
The "ping -n 2 127.0.0.1>nul" is in there only because there's not a "sleep" command included by default in windows.
This batch file is equivalent, but is much longer:
Code:
ECHO d:\testfile.dat 1 0x0 10>mypar.txt

sqlio.exe -kW -s20 -frandom -o1 -b4 -BH -LS -Fmypar.txt|find /i "IOs/sec">>sqlresults.txt
ping -n 2 127.0.0.1>nul
sqlio.exe -kW -s20 -frandom -o4 -b4 -BH -LS -Fmypar.txt|find /i "IOs/sec">>sqlresults.txt
ping -n 2 127.0.0.1>nul
sqlio.exe -kW -s20 -frandom -o16 -b4 -BH -LS -Fmypar.txt|find /i "IOs/sec">>sqlresults.txt
ping -n 2 127.0.0.1>nul
sqlio.exe -kW -s20 -frandom -o64 -b4 -BH -LS -Fmypar.txt|find /i "IOs/sec">>sqlresults.txt
ping -n 2 127.0.0.1>nul
sqlio.exe -kW -s20 -frandom -o256 -b4 -BH -LS -Fmypar.txt|find /i "IOs/sec">>sqlresults.txt
ping -n 2 127.0.0.1>nul

sqlio.exe -kW -s20 -frandom -o1 -b16 -BH -LS -Fmypar.txt|find /i "IOs/sec">>sqlresults.txt
ping -n 2 127.0.0.1>nul
...
etc., etc.
...
And here's the results on Open-E's Todd's test machine using a 4Gb FC link on both ends and a 3ware RAID card (only a single drive, but with write cache enabled on both the disk and controller) with about 512MB of memory on the card and about 2GB of system ram on the DSS side (but, I'm not sure that 32-bit FC works with more than 1GB of cache per volume):