[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22357: grep -f not only huge memory usage, but also huge time cost
|
From: |
Norihiro Tanaka |
|
Subject: |
bug#22357: grep -f not only huge memory usage, but also huge time cost |
|
Date: |
Tue, 15 Mar 2016 00:12:58 +0900 |
On Mon, 14 Mar 2016 14:31:50 +0800
JQK <address@hidden> wrote:
> # env time grep -w -f <(seq 200000) <(shuf -i 1-200000 -n 250)
> :
> 288.77user 64.23system 10:35.71elapsed 55%CPU (0avgtext+0avgdata
> 3492784maxresident)k
> 8967032inputs+0outputs (154389major+1493890minor)pagefaults 0swaps
The issue also reproceduces for following.
$ env time grep -w -f <(seq 200000) </dev/null
grep matcher searches with a lazy deterministic automaton, but it is not
good at the big pattern. This bug resembles bug#21763 and bug#22239.
- bug#22357: grep -f not only huge memory usage, but also huge time cost, JQK, 2016/03/10
- bug#22357: grep -f not only huge memory usage, but also huge time cost, Jim Meyering, 2016/03/10
- bug#22357: grep -f not only huge memory usage, but also huge time cost, JQK, 2016/03/11
- bug#22357: grep -f not only huge memory usage, but also huge time cost, Jim Meyering, 2016/03/11
- bug#22357: grep -f not only huge memory usage, but also huge time cost, JQK, 2016/03/14
- bug#22357: grep -f not only huge memory usage, but also huge time cost,
Norihiro Tanaka <=
- bug#22357: grep -f not only huge memory usage, but also huge time cost, Bruce Dubbs, 2016/03/14