* grep works too long and consumes more than 2 GB
@ 2020-02-18 17:56 Sergey A. Solodky
0 siblings, 0 replies; only message in thread
From: Sergey A. Solodky @ 2020-02-18 17:56 UTC (permalink / raw)
To: cygwin
[-- 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-02-18 17:56 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-18 17:56 grep works too long and consumes more than 2 GB Sergey A. Solodky
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).