From: Csaba Raduly <rcsaba@gmail.com>
To: Lee <ler762@gmail.com>
Cc: David Christensen <dpchrist@holgerdanske.com>,
cygwin list <cygwin@cygwin.com>
Subject: Re: Cygwin Perl has slowed in recent months
Date: Tue, 24 May 2022 10:25:43 +0200 [thread overview]
Message-ID: <CAEhDDbCOq5azJwRb_dpC4CgNFhe=w2n3ZJCcZ04H4VOFFMgrDg@mail.gmail.com> (raw)
In-Reply-To: <CAD8GWsvsNsF9w7NzxRDDDCwfcVkJp4_kVvwr6f7obCxi95-ZiQ@mail.gmail.com>
On Mon, 23 May 2022 at 20:47, Lee wrote:
>
> On 5/22/22, David Christensen <dpchrist@holgerdanske.com> 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.
* "The marvel is not that the bear dances well, but that the bear
dances at all" - Russian proverb
--
You can get very substantial performance improvements
by not doing the right thing. - Scott Meyers, An Effective C++11/14 Sampler
So if you're looking for a completely portable, 100% standards-conformant way
to get the wrong information: this is what you want. - Scott Meyers (C++TDaWYK)
next prev parent reply other threads:[~2022-05-24 8:25 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 [this message]
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='CAEhDDbCOq5azJwRb_dpC4CgNFhe=w2n3ZJCcZ04H4VOFFMgrDg@mail.gmail.com' \
--to=rcsaba@gmail.com \
--cc=cygwin@cygwin.com \
--cc=dpchrist@holgerdanske.com \
--cc=ler762@gmail.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).