public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Sergey A. Solodky" <ssolodky@evelopers.com>
To: cygwin@cygwin.com
Subject: grep works too long and consumes more than 2 GB
Date: Tue, 18 Feb 2020 17:56:00 -0000	[thread overview]
Message-ID: <9a788cff-0112-c9ec-f275-635b9dbb0897@evelopers.com> (raw)

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

Hi!

I encountered a grep issue. For now, I use the older version of Cygwin 
(32-bit, W2k3) in my test environment (for nightly tests). I'm going to 
migrate to a  modern platform, Windows Sever 2016 or 2019. In the 
archive attached is a sample to reproduce the issue. Here is a simple 
script trying counting strings in data file (56 strings) according to a 
pattern (a pretty long one, auto-generated by test) in the corresponding 
file. Both data file and pattern file are from the real test. This 
counting takes about 25 seconds on the older 32-bit system and more than 
2 and half hours on the newer one. See result_*.log files. In the last 
case grep fully uses 1 core of Core-i7 and consumes 2+ GB of memory. See 
screenshot.

The pattern contains two serial 'http_host' sub-patterns. Maybe they 
lead to the issue because another similar tests have no such a problem 
and they do not contain such 'pairs'.

-- 
Best wishes,
Sergey.
   



[-- Attachment #2: grep_issue.7z --]
[-- Type: application/octet-stream, Size: 19035 bytes --]

[-- Attachment #3: Type: text/plain, Size: 219 bytes --]


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

                 reply	other threads:[~2020-02-18 17:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9a788cff-0112-c9ec-f275-635b9dbb0897@evelopers.com \
    --to=ssolodky@evelopers.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).