Matt Shields wrote: > On 5/23/07, Les Mikesell <lesmikesell at gmail.com> wrote: >> > hey this part is fascinating, -so how would one practically deploy >> this, >> > -say 4 GB NICs and some supported hardware? for traffic 100 - 200 megs >> > daily perhaps this is too much? >> >> There's no such thing as 'too fast', but do you really need to complete >> you daily transfer in less than a second? On the practical side the >> underlying disks aren't going to be that fast anyway. >> > > You might if you have thousands of requests per second!!! A 200 Meg file is likely to be completely cached in the ftp server's RAM - and the cheapest way to get performance is to be sure that happens. > As a side note, when using the Promise VTrak and iSCSI it supports > multipath. It would probably be simpler to provide a separate interface or two for the ftp server <-> storage network than to go too crazy with multipathing. And for an ftp server you shouldn't need a great deal more speed on the filesystem side than you have on client connection side. -- Les Mikesell lesmikesell at gmail.com