public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Christensen <dpchrist@holgerdanske.com>
To: cygwin@cygwin.com
Subject: Cygwin Perl has slowed in recent months
Date: Tue, 17 May 2022 18:53:48 -0700	[thread overview]
Message-ID: <9a24b87b-e71d-9371-5d78-2b0f160adacd@holgerdanske.com> (raw)

cygwin:

I have a computer:

2022-05-17 18:46:12 dpchrist@dht4s3r1 ~/src/perl/Dpchrist-Perl
$ systeminfo | egrep '^OS (Name|Version)' ; uname -a ; cygcheck -c cygwin
OS Name:                   Microsoft Windows 7 Professional
OS Version:                6.1.7601 Service Pack 1 Build 7601
CYGWIN_NT-6.1 dht4s3r1 3.3.5(0.341/5/3) 2022-05-13 12:27 x86_64 Cygwin
Cygwin Package Information
Package              Version        Status
cygwin               3.3.5-1        OK


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


A few months ago, I seem to recall that Cygwin was about 4 times slower. 
  Now it is over 14 times slower.


Is this expected?  If not, how do I find the bottleneck?


TIA,

David

             reply	other threads:[~2022-05-18  1:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  1:53 David Christensen [this message]
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
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=9a24b87b-e71d-9371-5d78-2b0f160adacd@holgerdanske.com \
    --to=dpchrist@holgerdanske.com \
    --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).