3 ms·
> The resulting system can manage about 640 queries per second, compared to about 0.01 queries per second for ripgrep. They are trying to make a point about in
by finnh 3y ago
> The resulting system can manage about 640 queries per second, compared to about 0.01 queries per second for ripgrep.
They are trying to make a point about indexes, but it is overshadowed by the unit mismatch (distributed system QPS vs what sounds like single-machine ripgrep pace)
- deleted 3y ago[deleted]
- wtf_is_up 3y agoAccording to the engineering article [1], that ripgrep number is with 2048 cores combined with 115TB of data in memory. [1] https://github.blog/2023-02-06-the-technology-behind-githubs-new-code-search/ https://github.blog/2023-02-06-the-technology-behind-githubs...
- finnh 3y agoOK, thanks for that. Sounds like it's a valid comparison then.
- secondcoming 3y agoIsn't ripgrep also written in Rust?
- burntsushi 3y agoYes. ripgrep is used as a basis of comparison for that sentence. ripgrep wasn't GitHub's previous search implementation. (It never was. It's not the right tool for that scale.)