public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: gs-cygwin.com@gluelogic.com
To: David Christensen <dpchrist@holgerdanske.com>
Cc: cygwin@cygwin.com
Subject: Re: Cygwin Perl has slowed in recent months
Date: Wed, 25 May 2022 11:04:03 -0400	[thread overview]
Message-ID: <Yo5FY/4YsyN2KGjz@xps13> (raw)
In-Reply-To: <f21afd25-ff3c-657f-7711-6d66a142eb93@holgerdanske.com>

On Tue, May 24, 2022 at 11:36:21PM -0700, David Christensen wrote:
> I went back to the desktop computer that I have been using for Cygwin Perl
> testing:
> 
[...]
> 
> 'make test' produced the following result:
> 
> 99 wallclock secs ( 1.76 usr  0.41 sys + 342.21 cusr 375.40 csys = 719.78
> CPU)
> 
[...]
> I ran Cygwin setup-x86_64.exe version 2.918 and upgraded all Cygwin
> packages.
[...]
> I ran the cpan(1) shell and upgraded Perl modules:
[...]
> 
> 'make test' now produces:
> 
> 211 wallclock secs ( 2.39 usr  2.71 sys + 525.68 cusr 998.78 csys = 1529.57
> CPU)

You have merely demonstrated that there is a change in timing after
upgrading *all* of cygwin environment and packages.

Basic troubleshooting by any competent admin involves making changes
stepwise in steps as small as (reasonably) possible, and reperforming
tests each step.

Next step: go back to your older system and upgrade only the Perl
packages, then repeat the test.

If you are capable, try testing your cygwin environment on a different
machine, preferably not a corporate machine with hidden BLODA, and with
Microsoft Defender disabled (for the tests) (as previously asked by
others).

If you are capable, try testing older and newer Perl installations on a
different OS.

Annecdotally, I noticed about month or two ago that running my Perl
Test::Harness slowed down dramatically after an upgrade of both kernel
and packages on a Linux (*not Cygwin*) system.  I have not yet seen
compelling evidence from you that the slowdown is due to Cygwin, and
have seen data suggesting it is more directly related to Perl changes.

Other than your 'make test', do you have any evidence that anything else
has slowed down as dramatically between the old and new cywgin packages?
Any other shell scripts for which you tested the timing?
Any other Perl scripts for which you tested the timing?
  (and not run under 'make test')

  reply	other threads:[~2022-05-25 15:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  1:53 David Christensen
2022-05-21 17:55 ` Hans-Bernhard Bröker
2022-05-22 19:11   ` David Christensen
2022-05-23 18:47     ` Lee
2022-05-23 21:22       ` David Christensen
2022-05-24  8:25       ` Csaba Raduly
2022-05-24  8:47         ` Sam Edge
2022-05-24 15:03           ` David Christensen
2022-05-24 15:59             ` Sam Edge
2022-05-24 17:09               ` David Christensen
2022-05-24 19:31             ` Brian Inglis
2022-05-24 18:57 ` Achim Gratz
2022-05-25  6:36 ` David Christensen
2022-05-25 15:04   ` gs-cygwin.com [this message]
2022-05-25 20:06     ` David Christensen

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=Yo5FY/4YsyN2KGjz@xps13 \
    --to=gs-cygwin.com@gluelogic.com \
    --cc=cygwin@cygwin.com \
    --cc=dpchrist@holgerdanske.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).