[GLLUG] TCP/IP protocol efficiency

[Mike Szumlinski]

Access can be read only, that is perfectly fine.  The problem we are  
running into is that a full scan can be several hundred gigabytes.   
The problem seems to be that as soon as tcp/ip compression kicks in  
enough on these scans to get some solid throughput, it is done  
transferring that single file and starts all over again.  We are only  
getting about 6-7MB/sec out of gig-e using sftp currently

-Mike

On Jan 24, 2007, at 11:50 AM, Clay Dowling wrote:

>
> Mike Szumlinski wrote:
>> I've currently gotten involved with a project that is requiring I
>> reshare thousands of 12MB files out over TCP/IP from an XFS volume
>> on SuSe for use with Windows systems.  I have tried sftp and found
>> the transfer speed to be somewhat less than acceptable over gig-e and
>> was wondering if anyone had any input into another method of sharing
>> out the files that would be A) easier and B) faster.  Obviously samba
>> comes to mind, but I'm wondering if there are other easier ways to
>> tune this connection.  Any suggestions/ideas would be much  
>> appreciated.
>
> What's the context of the sharing?  What's the data and what will be
> accessing it?  That's going to be the biggest factor in what you use.
> Samba is hands-down the easiest way to make the data available to  
> windows
> clients, although http isn't a bad protocol either if the access  
> can be
> read-only.
>
> Clay
> -- 
> Simple Content Management
> http://www.ceamus.com
>