public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Christensen <dpchrist@holgerdanske.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin Perl has slowed in recent months
Date: Tue, 24 May 2022 23:36:21 -0700	[thread overview]
Message-ID: <f21afd25-ff3c-657f-7711-6d66a142eb93@holgerdanske.com> (raw)
In-Reply-To: <9a24b87b-e71d-9371-5d78-2b0f160adacd@holgerdanske.com>

[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]

cygwin:

I went back to the desktop computer that I have been using for Cygwin 
Perl testing:

motherboard:	Intel DQ67SW
processor:	Intel Core i7-2600S
memory:		Corsair CMV8GX3M2A1333C9 2 @ 4 GB
disk:		Intel SSD 520 Series 180 GB
OS Name:	Microsoft Windows 7 Professional
OS Version:	6.1.7601 Service Pack 1 Build 7601


See cygcheck-old.txt in the attached tarball for a listing of Cygwin 
packages installed.


'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 Windows Update, which indicated one optional update was available 
(Windows Defender).  I installed the update.


I ran Cygwin setup-x86_64.exe version 2.918 and upgraded all Cygwin 
packages.  See cygcheck-new.txt in the attached tarball for a listing of 
current Cygwin packages installed.


I ran the cpan(1) shell and upgraded Perl modules:

cpan[1]> upgrade /(.*)/


See cpan-upgrade.txt and current-perl-modules.txt in the attached 
tarball for a listing of Perl modules that were out-of-date and a 
listing of the current Perl modules installed.


'make test' now produces:

211 wallclock secs ( 2.39 usr  2.71 sys + 525.68 cusr 998.78 csys = 
1529.57 CPU)


David

[-- Attachment #2: cygwin-20220524-2330.tar.gz --]
[-- Type: application/gzip, Size: 14603 bytes --]

  parent reply	other threads:[~2022-05-25  6:36 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 [this message]
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=f21afd25-ff3c-657f-7711-6d66a142eb93@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).