Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 (Tek) 9/28/84 based on 9/17/84; site shark.UUCP Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!tektronix!orca!shark!charliem From: charliem@shark.UUCP (Charlie Mills) Newsgroups: net.unix Subject: Re: fgrep (isn't) Message-ID: <1459@shark.UUCP> Date: Wed, 10-Jul-85 14:22:48 EDT Article-I.D.: shark.1459 Posted: Wed Jul 10 14:22:48 1985 Date-Received: Sat, 13-Jul-85 08:10:25 EDT References: <495@unisoft.UUCP> Reply-To: tektronix!shark!charliem (Charlie Mills) Distribution: net Organization: Tektronix, Wilsonville OR Lines: 18 Summary: Under 4.2 on a vax, egrep is always faster than grep, running in about two thirds the time. But notice that egrep uses more memory, and there are one or two things grep can do that egrep can't (-v option). Fgrep is intended to be used with a string-list instead of a pattern. Emphasis on *list*. The string-list is usually taken from a file. I wonder why grep is faster than egrep on the Unisoft SysVr2 ports. Did AT&T or Unisoft speed up grep? Did Berkeley speed up egrep? Is memory size the issue? -- Charlie Mills UUCP: ..{ucbvax,decvax,uw-beaver,hplabs,ihnp4,allegra}!tektronix!shark!charliem CSNET: shark!charliem@tektronix ARPA: shark!charliem.tektronix@rand-relay USMail: M/S 61-277 Tektronix, Inc. P.O. Box 1000 Wilsonville, OR 97070