NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MPIO - slow speed
Hello! I have two ReadyNAS6 Pro boxes with the following configs: 1 box RDN6 pro/E7300/4gb/6*2Tb WD CB/4.2.27 FW 2 box RDN6 pro/E5300/2gb/6*2Tb WD CB/6.3.5 FW Other equipment: Juniper EX330...
Hello, mdgm.
Thanks for "the secret key" with two subnets - I've achived ~2*890mbps at READ with RND MPIO. Not so good as other vendors, but acceptable.
I think it will be better to add more MPIO specific information to ReadyNAS OS6 manual (and about supported LB policies too).
PS C:\> C:\SQLIO\sqlio.exe -s900 -kR -frandom -b8 -t8 -o16 -LS -BN D:\testfile.dat
sqlio v1.5.SG
using system counter for latency timings, 2474044 counts per second
8 threads reading for 900 secs from file D:\testfile.dat
using 8KB random IOs
enabling multiple I/Os per thread with 16 outstanding
buffering set to not use file nor disk caches (as is SQL Server)
using current size: 1048576 MB for file: D:\testfile.dat
initialization done
CUMULATIVE DATA:
throughput metrics:
IOs/sec: 25979.92
MBs/sec: 202.96
latency metrics:
Min_Latency(ms): 0
Avg_Latency(ms): 4
Max_Latency(ms): 75
histogram:
ms: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24+
%: 10 9 11 12 11 13 11 9 9 2 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0but what's the mess with WRITE??!!
PS C:\> C:\SQLIO\sqlio.exe -s900 -kW -frandom -b8 -t8 -o16 -LS -BN D:\testfile.dat
sqlio v1.5.SG
using system counter for latency timings, 2474044 counts per second
8 threads writing for 900 secs to file D:\testfile.dat
using 8KB random IOs
enabling multiple I/Os per thread with 16 outstanding
buffering set to not use file nor disk caches (as is SQL Server)
using current size: 1048576 MB for file: D:\testfile.dat
initialization done
CUMULATIVE DATA:
throughput metrics:
IOs/sec: 21.26
MBs/sec: 0.16
latency metrics:
Min_Latency(ms): 268
Avg_Latency(ms): 6005
Max_Latency(ms): 13647
histogram:
ms: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24+
%: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 100
PS C:\>that is unacceptable!
All MPIO performance is relate dto the client side not the readnas. to see good speed the client must plance the iscsi commands correctly.
The readynas just reponds to the reponse on whichver interface it sees. That is why 2 subnets important because otherwise the readynas will stick to one of the interfaces to send all traffic and so you get no ballancing
But now that you have subnets considered to ReadyNAs there is no extra configuration needed for MPIO. all decison over which interface to send the iscsi commands are on the client side.
I hope this makes sense
I do agreee we could do with some doicumentation in this area but it is not a common configurtation request we have sene but seems it is becoming more popopular.
On the read speed I would think at this point it is limited by interface speed and disk / volume maximum performane not really a readynas specific thing but I could be wrong. So Raid setup and disk performnce should be the limiting factors.
All MPIO performance is relate dto the client side not the readnas. to see good speed the client must plance the iscsi commands correctly.
The readynas just reponds to the reponse on whichver interface it sees. That is why 2 subnets important because otherwise the readynas will stick to one of the interfaces to send all traffic and so you get no ballancing
That is not complete correct because if I'm using Windows Server as iSCSI target I can use any subnets, including one subnet for all traffic even with 8 NICs both sides.
I do agreee we could do with some doicumentation in this area but it is not a common configurtation request we have sene but seems it is becoming more popopular.
Unfortunally I also have 4220 box. it's freesing, pausing, lagging and It's absolutly equal to this RND6 pro by FW, but have powerful hardware. So if NTGR presents 4220 as Enterprise (however RND6 pro is MID-Ent for NTGR) manuals MUST have enough explanation of devices logic. And if you presents iSCSI and MPIO - it's must work without some strange config particularly if there is no Vlan Tags and "management" interfaces (or OOB).
On the read speed I would think at this point it is limited by interface speed and disk / volume maximum performane not really a readynas specific thing but I could be wrong. So Raid setup and disk performnce should be the limiting factors.
This is not correct at all. it's nonsense.
there is no any way to get 20 IOPS and 0MB/sec from one SATA drive.
this is software bug
here is results of the same test at one sata drive (it's second drive at my work PC)
PS C:\Windows\system32> C:\SQLIO\sqlio.exe -s90 -kW -frandom -b8 -t8 -o16 -LS -BN D:\testfile.dat sqlio v1.5.SG using system counter for latency timings, 2728190 counts per second 8 threads writing for 90 secs to file D:\testfile.dat using 8KB random IOs enabling multiple I/Os per thread with 16 outstanding buffering set to not use file nor disk caches (as is SQL Server) using current size: 1048576 MB for file: D:\testfile.dat initialization done CUMULATIVE DATA: throughput metrics: IOs/sec: 135.66 MBs/sec: 1.05 latency metrics: Min_Latency(ms): 0 Avg_Latency(ms): 939 Max_Latency(ms): 1828 histogram: ms: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24+ %: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 99135 IOPS - that is good for one sata drive with such load
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
