ripgrep is faster than {grep, ag, git grep, ucg, pt, sift}

1. ripgrep

   1 395 65,004 8.9 Rust

   ripgrep recursively searches directories for a regex pattern while respecting your gitignore

   

   I've reun the same benchmark suite with ugrep, and it is not faster: https://github.com/BurntSushi/ripgrep/tree/master/benchsuite/runs/2022-12-16-archlinux-duff

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. xsv

   2 68 10,665 0.0 Rust

   Discontinued A fast CSV command line toolkit written in Rust.

   

4. ugrep

   3 29 3,173 8.4 C++

   🔍 ugrep 7.8 file pattern searcher -- a user-friendly, faster, more capable grep replacement. Includes a TUI, Google-like Boolean search with AND/OR/NOT, fuzzy search, hexdumps, searches (nested) archives (zip, 7z, tar, pax, cpio), compressed files (gz, Z, bz2, lzma, xz, lz4, zstd, brotli), pdfs, docs, and more

   

   These ripgrep announcements are getting a bit old, don't you think? Ripgrep hasn't improved or added new features since 2016. There are other fast alternatives with a lot more features, like ugrep and qgrep for example. Ugrep has fuzzy regex pattern search, archive search (even nested archives!), Boolean search queries like Google, interactive query TUI, hexdumps, and is compatible with GNU grep (ripgrep is not).

5. qgrep

   4 2 380 1.9 C++

   Fast regular expression grep for source code with incremental index updates

   

   These ripgrep announcements are getting a bit old, don't you think? Ripgrep hasn't improved or added new features since 2016. There are other fast alternatives with a lot more features, like ugrep and qgrep for example. Ugrep has fuzzy regex pattern search, archive search (even nested archives!), Boolean search queries like Google, interactive query TUI, hexdumps, and is compatible with GNU grep (ripgrep is not).

6. aho-corasick

   5 24 1,254 4.3 Rust

   A fast implementation of Aho-Corasick in Rust.

   

   Even putting aside all of that, it might be really hard to add some of the improvements ripgrep has to their engine. The single substring search is probably the lowest hanging fruit, because you can probably isolate that code path pretty well. The multi-substring search is next, but the algorithm is very complicated and not formally described anywhere. The best description of it, Teddy, is probably my own. (I did not invent it.)

Suggest a related project