Message-ID: <001401c651d0$872c9090$b3db87d4@multiplay.co.uk>
From: "Steven Hartland" <killing@multiplay.co.uk>
To: "'Cygwin List'" <cygwin@cygwin.com>
References: <048501c651b8$0862c1c0$a501a8c0@CAM.ARTIMI.COM>
Subject: Re: very poor cygwin scp performance in some situations
Date: Mon, 27 Mar 2006 19:59:02 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

----- Original Message ----- 
From: "Dave Korn"

> On 27 March 2006 16:39, Steven Hartland wrote:
> 
>> I've done quite a bit of digging and not found any real answers
>> on why cygwin's scp performance is so poor.
> 
>  See the thread about "select() too slow" last week for an explanation of the
> Nagle algorithm, how windoze's implementation of it appears to be crippling,
> and how using TCP_NODELAY can fix everything.  (Thread ran from 11 Mar to 19
> Mar). 

As a quick and dirty hack I channed set_nodelay into set_nonblock which
seems to be set on all the sockets but unfortunately it doesn't seem to help.
Anyone more familiar with the internals of openssh know where this might
done?

    Steve


================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137
or return the E.mail to postmaster@multiplay.co.uk.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/