From: Eliot Moss <moss@cs.umass.edu>
To: Gordon Grimes <Gordon.Grimes@nortonlifelock.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: possible grep V3.7 issue
Date: Mon, 6 Jun 2022 08:34:23 -0400 [thread overview]
Message-ID: <d3816695-b92c-f6e5-8d52-38a0b38ec479@cs.umass.edu> (raw)
In-Reply-To: <MN2PR13MB3885F6723E20AF4268581CC188A29@MN2PR13MB3885.namprd13.prod.outlook.com>
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://gnu.org/licenses/gpl.html.
> 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://git.sv.gnu.org/cgit/grep.git/tree/AUTHORS.
>
> 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:34 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 [this message]
2022-06-06 12:41 ` [EXT] " Gordon Grimes
2022-06-06 16:45 ` 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=d3816695-b92c-f6e5-8d52-38a0b38ec479@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=Gordon.Grimes@nortonlifelock.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).