X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EE243388A413 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=holgerdanske.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=holgerdanske.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=holgerdanske.com; s=nov-20210719-112354; t=1653412198; bh=hl91yaVtscp/rhrtaKtWZF5ijEOQt8wtkgEMdfmr3sQ=; h=Received:Message-ID:Date:MIME-Version:User-Agent:Subject: Content-Language:To:References:From:In-Reply-To:Content-Type: Content-Transfer-Encoding; b=s378eFTlUPFpE34dYeMj0lcvPiZjrPi4MTNA20JrLeuxbc6gNv/z94nsZ39ArXa5e ee00Nki9a7ZEpuK8dCbb+7L3oEC3dqmd+FLfpRaHl/KUBd7enX7E/+92KZ9cyqPN9N TW7bbOAm7ukkSsqQrx/kxVahCvUUBEQkPBsoltO9VMW2aR7SzfUJ5m7ItYG4F5+rqR RroISBsRqTcb4unT1iT9MNXJL3X891DfRiFH+XbdLJzW3DBKXwKiiyqEiXLGypXbYq KfYN86hA8M3t8z3Jj1iiXOPU4gp9MpM8MKjCVCTH0xew0RInKX0hNkOy7sSiLpo0JW 94zL6GYoPn5bWmwYPHxLoGDChIv/1TL27XWN84Q6EX2uSZNMgk62/M7ApqFwN/FrPN upmGSyX5MLT1asM/gzIut6ub+WcmIbEsHUCcZW5Au1voTWLa9Q+L+ROkwYurdci9UV prVHuVbYs/BaG30qzs3MD91Gz5OuS98VOUffvlu/I1I+eBLiJRrctBV5tlH2nvSUXF vDjmSgpw/Tyj6NcMK+37Uemf1iVCeC8F1+K1RZ71k0XdYOwIek1OxVuK4hg2J8iprZ 4lMhrnv2e1kM1vY2k774K44Dphekvz0gW5KKDeAiPFGdFNaqYlw063vjOkEFYSiYdV W1vhbFDFQdqxGp1ak94inowk= Message-ID: <28084444-dec3-d3b2-bfe5-b9472f2e3f0f@holgerdanske.com> Date: Tue, 24 May 2022 10:09:57 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: Cygwin Perl has slowed in recent months Content-Language: en-US To: cygwin AT cygwin DOT com References: <9a24b87b-e71d-9371-5d78-2b0f160adacd AT holgerdanske DOT com> <69f7b5b2-0730-bce2-90d8-95a7fde0a15f AT t-online DOT de>

<82fcdaf2-3fff-5244-6a47-71ba768a0908 AT gmx DOT com> From: David Christensen In-Reply-To: <82fcdaf2-3fff-5244-6a47-71ba768a0908@gmx.com> X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00, BODY_8BITS, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT 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: , Content-Type: text/plain; charset="utf-8"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 24OHANxC013272 On 5/24/22 08:59, Sam Edge wrote: > On 24/05/2022 16:03, David Christensen wrote: >> On 5/24/22 01:47, Sam Edge wrote: >>> On 24/05/2022 09:25, Csaba Raduly wrote: >>> > On Mon, 23 May 2022 at 20:47, Lee wrote: >>> >> >>> >> On 5/22/22, David Christensen wrote: >>> >>> On 5/21/22 10:55, Hans-Bernhard Bröker wrote: >>> >>>> Am 18.05.2022 um 03:53 schrieb David Christensen: >>> >>>> >>> >>>> > I am working on a Perl module that runs on various Unix-like >>> platforms. >>> >>>> > When I 'make test' on similar computers: >>> >>>> > >>> >>>> > FreeBSD 12.3-RELEASE 28 wallclock secs >>> >>>> > Debian GNU/Linux 11.3 31 wallclock secs >>> >>>> > macOS 11.6.2 36 wallclock secs >>> >>>> > Windows 7 / Cygwin 3.3.5-1 509 wallclock secs >>> >>>> >>> >>>> Given the complete lack of information about what that Perl >>> module of >>> >>>> yours might be doing, that's hard to have a meaningful discussion >>> about. >>> >>> >>> >>> >>> >>> Thank you for the response. I was hoping there was a known issue. >>> >>> Apparently, not. >>> >> >>> >> What I consider a well known issue is that process start up time is >>> >> _very_ slow. If your 'make test' starts lots of processes that >>> could >>> >> be a problem. >>> >> >>> > >>> > While Cygwin''s fork emulation is indeed slow (I once measured >>> 1000:1 >>> > between Cygwin and Linux * ), >>> > "make test" likely started roughly the same number of processes >>> "then" >>> > as it does "now". >>> > In which case the increase in the run time could be attributed to >>> Cygwin. >>> >>> Indeed. >>> >>> But perhaps what the Cygwin core and/or Cygwin Perl maintainers need >>> is a >>> simple test case Perl script that can be shown to be much slower on the >>> current >>> releases than it was on a named earlier pair of releases. And maybe some >>> testing by the original poster to see if it is the Cygwin or Perl >>> release >>> change that causes the issue. >>> >>> Anecdotal observations do not an issue report make. ;-) >> >> >> So, we are discussing running a Perl benchmark for various >> combinations of Cygwin version and/or Cygwin Perl version. That is an >> O(n) and/or O(n**2) problem. >> >> >> If multiple benchmarks are considered, increase the O() exponent by one. >> >> >> If multiple versions of Windows are considered, increase the O() >> exponent by one. >> >> >> If multiple computers are considered, increase the O() exponent by one. >> >> >> Does the Cygwin project do any of the above? If so, how? Where are >> the test plans and assets? Where is the raw data? Where are the >> reports? >> >> >> If end users are expected to do the above, please advise: >> >> 1. How to install multiple versions of Cygwin on Windows 7 >> Professional 64-bit Service Pack 1 on an x86_64 computer such that >> each instance of Cygwin does not interact with any other instance of >> Cygwin. >> >> 2. How to install multiple versions of Cygwin Perl on each of many >> Cygwin installations on Windows 7 Professional 64-bit Service Pack 1 >> on an x86_64 computer such that each instance of Cygwin Perl does not >> interact with any other instance of Cygwin Perl or Cygwin. >> >> 3. What is a suitable Perl benchmark? >> >> >> David >> > The Cygwin core & Perl maintainers do not get paid for their work. I do not get paid for working on Cygwin and/or Perl. But, I have been paid for using and programming both. > If you believe you have spotted a regression, it's up to you to isolate > at what revision of Perl or of Cygwin core it started to happen. If Cygwin provides me with the means; fair enough. > You can > get older revisions of Cygwin & Perl from the Cygwin Time Machine > (GFGI). https://html.duckduckgo.com/html?q=site%3Acygwin.org%20cygwin%20time%20machine https://cygwin.cygwin.narkive.com/cSRkGFjw/time-machine http://www.fruitbat.org/Cygwin/index.html#cygwincirca http://www.crouchingtigerhiddenfruitbat.org/Cygwin/timemachine.html I built a similar hack years ago. GFGI Programming Systems Product > You can have as many parallel installations of Cygwin and its > packages as you like simply by specifying different install paths when > running the setup program (RTFM). Section? Page? > Like most FOSS, Cygwin & its packages are provided with no warranty. https://cygwin.org/faq.html#faq.what.free > If they are so vital to your business, you need to be doing regression > testing yourself before upgrading production systems Have you been spying on me? ;-) > and maintaining > your own Cygwin repo so you have a copy of the production releases. https://cygwin.org/faq.html#faq.what.version https://cygwin.org/faq.html#faq.setup.old-versions I would say "disappointing", but I think you found the answer (below). > This is all SOP for using FOSS in a business context, TIMTOWTDI. > unless you're > willing to pay someone else to do it for you, > which is how Red Hat et al > make their money. I think you have found the answer. David -- 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