Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-T2-Posting-ID: IBEbVI5rtGvBBu0aty/gAw== Message-ID: <426D48F4.5040908@ege.cc> Date: Mon, 25 Apr 2005 21:45:56 +0200 From: Bernhard Ege User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: scp/ssh between two cygwin installations very slow References: <426D28E3 DOT 4080303 AT ege DOT cc> In-Reply-To: <426D28E3.4080303@ege.cc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Bernhard Ege wrote: > I am trying to copy an 800MB file from my pc to my laptop. The pc has > cygwin and cygwins sshd running and from the laptop I use the scp > command to copy the file. > > Result: 190kB/s with low (1-5%) cpu usage on both machines. > > Expected result: at least 2-3MBps with somewhat higher cpuusage on both > machines. Doh. I completely forgot that in my .ssh/config I had ssh call a script using the ProxyCommand. That command is a shell script that detects which network I am connected to (company or my own) and uses a tunneling ssh command to the destination if on the company network or a direct connection using "connect" if on my own network. The connect command is a fairly simple program that redirects stdin/stdout to a host:port. This way, I can either use a ssh to host:port if tunneling is required to connect to host:port if not. The problem is that cygwin has a very low throughput using the script with the connect command. I guess it could be related to the slow pipe problem mentioned earlier (but was supposedly fixed). I have tried without the ProxyCommand and the speed returned to an acceptable 1.5MBps. I hope Cygwin can be fixed so the speed returns to normal :-) Thanks, Bernhard Ege -- 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/