From: Gordon Grimes <Gordon.Grimes@nortonlifelock.com>
To: "moss@cs.umass.edu" <moss@cs.umass.edu>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [EXT] Re: possible grep V3.7 issue
Date: Mon, 6 Jun 2022 12:41:35 +0000 [thread overview]
Message-ID: <MN2PR13MB388552D979904FD099EC39D688A29@MN2PR13MB3885.namprd13.prod.outlook.com> (raw)
In-Reply-To: <d3816695-b92c-f6e5-8d52-38a0b38ec479@cs.umass.edu>
Thanks Elliot.
Yeah, I suspected this wasn't 100% reproducible or else it'd have been reported/addressed by now. As you say, perhaps there's some idiosyncrasy with my system/setup. If there's a wave of reporting a similar issue then perhaps it's worth a look (e.g. perhaps a recent MS update triggered this). Anyway, unless/until that happens, I'll simply stick with V3.6.
Thanks for taking a look.
-g-
-----Original Message-----
From: Eliot Moss <moss@cs.umass.edu>
Sent: Monday, June 6, 2022 8:34 AM
To: Gordon Grimes <Gordon.Grimes@nortonlifelock.com>; cygwin@cygwin.com
Subject: [EXT] Re: possible grep V3.7 issue
On 6/6/2022 8:26 AM, Gordon Grimes via Cygwin wrote:
> Hi,
>
> I wanted to let you know about a possible issue I found in grep v3.7. I run Cygwin and recently downgraded ‘grep’ to v3.6 from v3.7 to address a performance issue (shown below).
> I just thought you’d want to know (V3.6 is working well, so I’m in a
> good place 😊 ) Enjoy,
> -g-
>
>
> % time echo hi | grep h
> hi
>
> real 0m7.442s
> user 0m0.030s
> sys 0m6.576s
>
> % /usr/bin/grep --version
> grep (GNU grep) 3.7
> Packaged by Cygwin (3.7-2)
> Copyright (C) 2021 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgnu.org%2Flicenses%2Fgpl.html&data=05%7C01%7CGordon.Grimes%40nortonlifelock.com%7C640f66e158104f7486ea08da47b8e328%7C94986b1d466f4fc0ab4b5c725603deab%7C0%7C0%7C637901156666044572%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=FujGNPbnS6TMO8I1RT%2FuczWHhImX6KnEUnLWC5EYYTE%3D&reserved=0.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by Mike Haertel and others; see
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.sv.gnu.org%2Fcgit%2Fgrep.git%2Ftree%2FAUTHORS&data=05%7C01%7CGordon.Grimes%40nortonlifelock.com%7C640f66e158104f7486ea08da47b8e328%7C94986b1d466f4fc0ab4b5c725603deab%7C0%7C0%7C637901156666044572%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=yXCYAppkPpbDwkD1h2BPA%2B5PPE6QYLRvmVHxvUwxP34%3D&reserved=0.
>
> After the downgrade…
>
> % time echo hi | grep h
> hi
>
> real 0m0.292s
> user 0m0.015s
> sys 0m0.124s
I'm running 3.7-2 and get timing similar to what you give for 3.6:
real 0m0.167s
user 0m0.015s
sys 0m0.061s
Not sure what to say unless, if I downgraded, it would be an order of magnitude faster ...
I wonder if maybe the new version triggers some anti-virus activity or something like that.
Eliot Moss
next prev parent reply other threads:[~2022-06-06 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MN2PR13MB388514876921EBCBC0BB38FA88D79@MN2PR13MB3885.namprd13.prod.outlook.com>
2022-06-06 12:26 ` Gordon Grimes
2022-06-06 12:34 ` Eliot Moss
2022-06-06 12:41 ` Gordon Grimes [this message]
2022-06-06 16:45 ` [EXT] " Brian Inglis
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=MN2PR13MB388552D979904FD099EC39D688A29@MN2PR13MB3885.namprd13.prod.outlook.com \
--to=gordon.grimes@nortonlifelock.com \
--cc=cygwin@cygwin.com \
--cc=moss@cs.umass.edu \
/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).