3 ms·

this is a highly misleading comparison. something slightly more accurate (although this time somewhat more hg-biased): $ time taskset -c 2 hg grep CUDA >/d

by Hello71 10y ago

this is a highly misleading comparison. something slightly more accurate (although this time somewhat more hg-biased): $ time taskset -c 2 hg grep CUDA >/dev/null taskset -c 2 hg grep CUDA > /dev/null 25.04s user 0.46s system 99% cpu 25.514 total $ time taskset -c 2 sh -c 'git grep --cached -l CUDA | xargs -n 1 git blame >/dev/null' taskset -c 2 sh -c 4.85s user 0.13s system 97% cpu 5.097 total

jlebar 10y ago
> this is a highly misleading comparison. Why? When I do hg grep, it doesn't show me blame or anything; the output looks almost identical to the output of git grep. If it's doing work and then throwing it away, why is it fair to force git to do the same work and then also throw it away? (I'll also point out that git is still 5x faster in this comparison. :)