Actually no. Being somewhat familiar with grep, I started piping find's output as a general practice as soon as I discovered (several years ago) that it would output a list of everything below a given tree point. I only noticed that find alone was slower today when I actually read the man page, figured out the -name options, and decided to try it.
Piping through grep seems to be more flexible as well, though I may have missed some options somewhere in my cursory read.
Well, I meant in direct temporal order, rather than long-term.
I've noticed that grepping and such are much, much faster after the first attempt, which I expect means that the OS has cached these files in available memory. (And this is why I'd *love* an SSD.)
Yeah, I wasn't really clear there. I ran find|grep -i first, then thought about it and looked at the man page, then ran find -iregex. So if anything, find alone should have benefitted from the caching....
Hell, I dunno. Maybe it's just another instance of my computers screwing with me.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
branchandroot
no subject
Date: 2010-02-28 12:33 am (UTC)no subject
Date: 2010-02-28 01:31 am (UTC)Piping through grep seems to be more flexible as well, though I may have missed some options somewhere in my cursory read.
no subject
Date: 2010-02-28 03:32 am (UTC)I've noticed that grepping and such are much, much faster after the first attempt, which I expect means that the OS has cached these files in available memory. (And this is why I'd *love* an SSD.)
no subject
Date: 2010-02-28 04:59 am (UTC)Hell, I dunno. Maybe it's just another instance of my computers screwing with me.