3 ms·

That is just insanely fast. OP are you author?

• ditoa 14y ago
  Agreed it is very fast but I believe it is only searching against 3.4.4?
  • ditoa 14y ago
    Their about page [0] suggests it is just 3.4.4. Still pretty impressive though :) [0] http://codesear.ch/about http://codesear.ch/about
  • eklitzke 14y ago
    I'm the author of this. I think I can index a lot more source code and still keep the speed. The important part of the index, the ngrams table, is only 400M or so of space and compresses pretty well. I had a test index at one point that was also indexing all of the C code in these projects: clang-3.1.src gcc-4.7.1 ghc-7.4.1 linux-3.4.4 llvm-3.1.src lua-5.2.0 openjdk perl-5.16.0 php-5.4.4 Python-2.7.3 Python-3.2.3 ruby-1.9.3-p194 And it only increased the size of the index by about 50%.
• mdwrigh2 14y ago
  You can actually run essentially the same thing over your own code with http://code.google.com/p/codesearch http://code.google.com/p/codesearch (written by the author of the article codesear.ch is based off).
• jstanley 14y ago
  It's not that fast. With a hot cache "grep -rn mmap /usr/src/linux/" runs in 0.3s on my desktop machine. EDIT: Don't get me wrong, the code behind this is awesome. I just can't help but think there could be something bigger to search, that is infeasible to do on my desktop. What about all of the code from the Debian repositories or something?
  • eklitzke 14y ago
    This doesn't require the working set to be in memory (in fact, the size of the index is larger than the amount of memory that I have on the machine).