X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 30 Jun 2009 13:26:17 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Call for TESTING (was Re: [1.7.0-50] scp progress counter flies through first 175 MB or so) Message-ID: <20090630112617.GS30864@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090625101039 DOT GP7289 AT calimero DOT vinschen DOT de> <20090625140508 DOT GA17040 AT ednor DOT casa DOT cgf DOT cx> <20090625143651 DOT GR7289 AT calimero DOT vinschen DOT de> <20090625145005 DOT GB18338 AT ednor DOT casa DOT cgf DOT cx> <20090628193155 DOT GA10407 AT ednor DOT casa DOT cgf DOT cx> <20090629092857 DOT GZ30864 AT calimero DOT vinschen DOT de> <20090629095322 DOT GD30864 AT calimero DOT vinschen DOT de> <20090629142348 DOT GB19123 AT ednor DOT casa DOT cgf DOT cx> <20090629144030 DOT GC19123 AT ednor DOT casa DOT cgf DOT cx> <4A490F0E DOT 6040806 AT etr-usa DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A490F0E.6040806@etr-usa.com> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Jun 29 12:59, Warren Young wrote: > I scp'd a 1.6 GB file back and forth to a Linux server over GigE to a > fast new RAID-10. I tested 1.7.0-50 and 20090629. > > Results: > > On a 32-bit XP box, 1.7.0-50 gives about 15 MByte/sec for both upload > and download. (This box can't really hit GigE speeds due to crappy > cabling and a low-quality switch.) On switching to the snapshot, the > download speed is about the same, but upload is cut to 4-5 MB/sec. > > On a 64-bit Vista box, 1.7.0-50 gives inconsistent behavior. Download > behaves as it should: ~45 MB/sec here, due to better switch and cabling. > But, uploading with scp gives the reported behavior: the scp status > fills out to 100% very fast but then scp doesn't finish running for > quite a while. It's like it's buffering a big fraction of the 1.6 GB, > which isn't impossible, since this box has 12 GB of RAM. (Core i7, > DDR3, wheee!) > > After switching to the snapshot on that Vista-64 box, the scp progress > display becomes useful, growing steadily as scp runs. Unfortunately, my > upload speed is down to around 5 MB/sec here, just as on the XP box. > > A different non-Cygwin scp client I have here can manage much faster > transfer speeds, so I can rule out disk and network bottlenecks. The > slowdowns are in Cygwin itself or the Cygwin scp port. > > I can rule out a problem in the general network I/O handling: changing > the DLL doesn't seem to affect ttcp results materially. It's either scp > or the way scp uses cygwin1.dll. I just had a look into this and I think I found a way to raise the outbound transfer rates somewhat. The outbound speed is always slower than the inbound speed, no matter what I try. However, I'm now at a point where it might be more acceptable. One of my test machines, a 2K8 32 bit box has the following scp transfer rates under 1.5.25: inbound: 17.2 MB/s outbound: 3.5 MB/s With the latest snapshot: inbound: 21.5 MB/s outbound: 4.2 MB/s With the latest from CVS: inbound: 21.5 MB/s outbound: 11.5 MB/s What's still not clear is why the ssh process takes so much CPU. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple