From: David Christensen <dpchrist@holgerdanske.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin Perl has slowed in recent months
Date: Mon, 23 May 2022 14:22:00 -0700 [thread overview]
Message-ID: <fd023c43-af9d-1dc5-13d6-fc581148eebc@holgerdanske.com> (raw)
In-Reply-To: <CAD8GWsvsNsF9w7NzxRDDDCwfcVkJp4_kVvwr6f7obCxi95-ZiQ@mail.gmail.com>
On 5/23/22 11: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
>> I was hoping there was a known issue.
> 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.
[Replying to off-list message.]
Thank you for the reply.
'make test' starts a large number of processes -- perhaps a thousand.
> Another huge slowdown is Windows Defender. Try turning that off and
> seeing how long your 'make test' takes then.
Of all the test scripts, 02-compile.t consumes the most time on all
platforms.
Using 02-compile.t as a benchmark, here is the compile time with Windows
Defender enabled:
$ time perl -Ilib t/02-compile.t
<snip>
real 2m1.404s
user 3m20.490s
sys 4m24.476s
Here is the compile time with Windows Defender disabled:
$ time perl -Ilib t/02-compile.t
<snip>
real 1m56.606s
user 3m14.374s
sys 4m20.106s
Both of the above tests were run in Cygwin64 Terminal. Using Debian and
SSH:
$ time perl -Ilib t/02-compile.t
<snip>
real 1m18.733s
user 2m32.187s
sys 2m29.652s
So, Cygwin64 Terminal is also a problem.
In all cases, Resource Monitor indicates the script is CPU bound.
David
next prev parent reply other threads:[~2022-05-23 21:22 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 [this message]
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=fd023c43-af9d-1dc5-13d6-fc581148eebc@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).