From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout.easymail.ca (mailout.easymail.ca [64.68.200.34]) by sourceware.org (Postfix) with ESMTPS id 183873858C27 for ; Tue, 31 Aug 2021 19:53:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 183873858C27 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=house.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=house.org Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 2F310110A72 for ; Tue, 31 Aug 2021 19:53:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at emo02-pco.easydns.vpn Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo02-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLkTwla1PrZn for ; Tue, 31 Aug 2021 19:53:03 +0000 (UTC) Received: from tringa.house.org (S0106bcee7b974edc.gv.shawcable.net [24.108.53.141]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id A741B110A62 for ; Tue, 31 Aug 2021 19:53:03 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: cygrunsrv + sshd + rsync = 20 times too slow -- throttled? From: Chris Roehrig In-Reply-To: <58bdc0c3-d843-343f-d88e-c8a44ec33a15@cornell.edu> Date: Tue, 31 Aug 2021 12:53:02 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <3DB951FB-FC3F-4EE8-B5E0-6137B305B873@house.org> References: <41A583E1-C8E7-42AB-9F24-EEC33A41EC60@house.org> <20210825201845.07b6400b79dc5558a7761efe@nifty.ne.jp> <20210826062934.54f2f2216021c095bb7ba13b@nifty.ne.jp> <3b560051-ab27-f392-ca4b-d1fd9b5733b0@cornell.edu> <20210827202440.47706fc2fc07c5e9a1bc0047@nifty.ne.jp> <4f2cb5f3-ce9c-c617-f65f-841a5eca096e@cornell.edu> <20210828022111.91ef5b4ff24f6da9fadb489e@nifty.ne.jp> <20210828184102.f2206a8a9e5fe5cf24bf5e45@nifty.ne.jp> <20210829180729.48b4e877f773cb3980c5766d@nifty.ne.jp> <789f056a-f164-d71d-1dc9-230f5a41846d@cornell.edu> <46906957-5850-4D7E-8D5A-EFF3C4068C0D@house.org> <58bdc0c3-d843-343f-d88e-c8a44ec33a15@cornell.edu> To: Ken Brown via Cygwin X-Mailer: Apple Mail (2.1499) X-Spam-Status: No, score=-3.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Aug 2021 19:53:19 -0000 Thanks, I did some more tests: scp also shows no improvement with topic/pipe. I tried = running cygsshd with CYGWIN=3Dpipe_byte as well as empty (in the = registry = HKLM/SYSTEM/CurrentControlSet/Services/cygsshd/Parameters/Environment/), = using net stop cygsshd + net start cygsshd to restart it. Not sure if = that CYGWIN only applies to cygsshd or to all cygwin tasks. I get the procps error just running 'procps' command with no args from = mintty (/usr/bin/procps). Looking at the procps-ng source (procps-ng = 3.3.17-1 is what setup_x86_64 reports as my installed package), it = appears to be a mmap() failure. I'm wondering if I built/installed cygwin1.dll correctly because I don't = get the procps error using the latest stock cygwin1.dll as installed by = setup_x86_64. -- Chris On Tue Aug 31 2021, at 12:05 PM, Ken Brown via Cygwin = wrote: > On 8/30/2021 7:58 PM, Chris Roehrig wrote: >> I got it to build and tried out the topic/pipe branch (checked out on = Monday around 4:30pm PDT): >> 1. I didn't see any improvement in my sshd+rsync time, still 3-4 = MB/sec. >> 2. I get the following error from procps: procps:ps/output.c:2195: = please report this bug >> (I also get this using the main branch build). >> I first updated my cygwin normally using setup-x86_64.exe, then built = and copied only the cygwin1.dll into /bin from the install/bin directory = (quitting all cygwin tasks first). >=20 > Thanks for testing. >=20 > We're still working on this. (The discussion has moved to the = cygwin-developers mailing list.) I'll let you know when it's stable, = and maybe you can try again. >=20 > As to the procps error, can you give details so that someone can try = to reproduce it and debug it? >=20 > Ken >=20 > --=20 > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation: https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple