Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a few gigabytes of source code.

using recursive grep for a term can take a while.

I am using ext3.

Is there a faster way? Would using find be faster and if so why? Would using a filesystem like XFS give noticeably better results?

share|improve this question

migrated from Dec 16 '09 at 22:43

This question came from our site for professional and enthusiast programmers.

with exec it can use grep which would be faster than just using grep – Joshxtothe4 Dec 16 '09 at 20:46
and why would that be faster? – akira Dec 16 '09 at 22:57

Have you tried ack? It works pretty well here, on a 1mm+ sized codebase.

share|improve this answer
ack is easier and faster than using find | grep, and I often use it, but it doesn't index the results anywhere for later use. – njd Feb 9 '10 at 12:49

You can get better performance with agrep, which uses a novel bitmasking algorithm for search.

If you're looking for symbols, ctags or etags might work well enough to build an index for search.

share|improve this answer
+1 ctags ...... – Ewan Dec 16 '09 at 20:51
Ctags indexes the results, so you can search quickly from your editor. Darren Hiebert's Exuberant Ctags ( has improved options for recursive searching. – njd Feb 9 '10 at 12:54

The only way you'll get a significant improvement over grep is to use an indexed search system like Strigi. The filesystem makes very little difference unless you have a huge number of very small files.

share|improve this answer

This should likely be on superuser.

Grepping is not the ideal solution to your problem since it performs a linear search.

Index your files for search using a desktop indexing solution such as Beagle or Google Desktop.

share|improve this answer

I don't think the FS is going to make a big difference; chances are it's compute bound. You could check this using top to see if your CPUs are smoking.

You could also post your regexp here and let the smart people of SO have a crack at optimizing it. There are a variety of techniques for avoiding backtracking, etc.

share|improve this answer
fgrep is faster because it doesn't use regular expressions, it only searches for fixed strings. It's just an alias for grep -F. – Tim Sylvester Dec 16 '09 at 20:44
Right you are, thanks. I removed that part of my suggestion. – Carl Smotricz Dec 16 '09 at 20:50

Here is what I understand -

  • You are searching source code for a term
  • You'd like to see which source files use that term
  • You probably have thousands of files (adding up to GBs)
  • Do you want to know all the occurrences of 'term' within each file or a yes/no indication of whether its been used in a file or not? (the -l flag does this).

You can use the policy of divide-and-rule. Partition your set into multiple file-sets, run multiple greps parallely.

Not sure if your need is a one-off thing or something repetitive in nature.

share|improve this answer

If you only need to grep a subset of files then use find first. For example to only grep .h header files:

find path/to/source -name *.h -print0 | xargs -0 grep pattern

This will be faster since you're only accessing filenames most of the time, rather than file contents, which means many fewer disc accesses.

share|improve this answer
Better: find path/to/source -name *.h -exec grep pattern {} \; – Ewan Dec 16 '09 at 20:50
Even better: find path/to/source -name *.h -exec grep pattern {} \+ (less grep invocations) – filiprem Dec 16 '09 at 22:39

You must log in to answer this question.