public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Steven Hartland" <killing@multiplay.co.uk>
To: <cygwin@cygwin.com>
Subject: Re: socket performance (was Re: Building cygwin1.dll)
Date: Tue, 10 Jan 2012 18:23:00 -0000	[thread overview]
Message-ID: <6E23B1B3BBEF4CFFB88FEB74F1DCF20E@multiplay.co.uk> (raw)
In-Reply-To: <20120110172621.GJ2292@calimero.vinschen.de>

----- Original Message ----- 
From: "Corinna Vinschen" 
> Well, the file I downloaded was a self-extracting zip archive and the
> file it contains is called Windows6.1-KB983528-x64.msu, so I'm fairly
> certain it's the right one for an AMD64 system.

Windows6.1-KB983528-x64.msu is the file I have here too so unless
there's something else a play i.e. running as Administrator UAC rubish?

>> If this bug is effecting your you need to ensure that you make no connections
>> using the machine that could possibly trigger the throughput issues prior to
>> testing. Otherwise you'll be using a tcp stack without scaling.
> 
> Sounds tricky.  The laptop is a domain member and it's not in the same
> room with me so I'm running this via rdesktop.  But that would be fixable.
> 
> However, if this issue is the problem, then why is sftp fast and only scp
> and rsync slow?  I can reproduce this at will, not only once in the
> right order.

Hmm that would indeed not be explained by the KB iirc there are some
internal differences between the way sftp and scp transfer data.

Do you have a wireshark dump of the two transfers we could examine?

    Regards
    Steve


--
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

  reply	other threads:[~2012-01-10 18:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04 13:49 Building cygwin1.dll Johan van den Berg
2012-01-04 14:25 ` marco atzeri
2012-01-04 19:26   ` Johan van den Berg
2012-01-09 13:44     ` socket performance (was Re: Building cygwin1.dll) Corinna Vinschen
2012-01-09 16:37       ` Václav Zeman
2012-01-10  8:46         ` Corinna Vinschen
2012-01-10  7:22       ` socket performance Henry S. Thompson
2012-01-10  7:53         ` Daniel Colascione
2012-01-10 12:46       ` socket performance (was Re: Building cygwin1.dll) Johan van den Berg
2012-01-10 14:46         ` Corinna Vinschen
2012-01-10 15:25           ` Steven Hartland
2012-01-10 16:28             ` Corinna Vinschen
2012-01-10 16:39               ` Corinna Vinschen
2012-01-10 17:05               ` Steven Hartland
2012-01-10 17:27                 ` Corinna Vinschen
2012-01-10 18:23                   ` Steven Hartland [this message]
2012-01-11 14:05                     ` Corinna Vinschen
2012-01-11 14:20                       ` Carson Chittom
2012-01-11 14:43                         ` Corinna Vinschen
2012-01-11  6:25           ` Johan van den Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6E23B1B3BBEF4CFFB88FEB74F1DCF20E@multiplay.co.uk \
    --to=killing@multiplay.co.uk \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).