bug-grep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug-grep] egrep: memory exhausted


From: Dan Stromberg
Subject: [bug-grep] egrep: memory exhausted
Date: Fri, 11 Mar 2005 18:13:16 -0800
User-agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.)

This command eventually gave "egrep: memory exhausted":

seki-root> reblock -e 75216016 $(expr 1024 \* 1024) 300 <
/dev/mapper/VolGroup00-LogVol00 | mtee 'egrep --binary-files=text -i -B
1000 -A 1000 dptutil > dptutil-hits' 'egrep --binary-files=text -i -B 1000
-A 1000 dptmgr > dptmgr-hits'
stdin seems seekable, but file length is 0 - no exact percentages
Estimated filetransfer size is 77021200384 bytes Estimated percentages
will only be as accurate as your size estimate Creating 2 pipes
popening egrep --binary-files=text -i -B 1000 -A 1000 dptutil >
dptutil-hits popening egrep --binary-files=text -i -B 1000 -A 1000 dptmgr
> dptmgr-hits
(estimate: 0.1%  0s 56m 11h) Kbytes: 106496.0  Mbits/s: 13.6 Gbytes/hr:
6.0  min: 1.0 (estimate: 0.2%  9s 12m 12h) Kbytes: 214016.0 Mbits/s: 13.3 
Gbytes/hr: 5.8  min: 2.0 (estimate: 0.3%  58s 58m 11h) Kbytes: 257024.0 
Mbits/s: 13.5  Gbytes/hr: 5.9  min: 2.4      
...

references:
http://dcs.nac.uci.edu/~strombrg/reblock.html
http://dcs.nac.uci.edu/~strombrg/mtee.html

I got the task done by dusting off my old bgrep program, but I expect that
it's vastly slower than egrep.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]