Hacker News Reader

So I have to wonder about the performance difference between his sloccount and loc (https://github.com/cgag/loc) which is so fast it always makes me think that it hasn't done anything (same as ripgrep).

I'm like 98% sure loc will be faster, but it would be interesting to know by how much.

View on HN

so I ran this test using the linux source code. I warmed everything to prevent caching/buffering advantages.

For loc the best time was: 55.425s and the worst was: 1m30.557s

For loccount the best time was: 42.345s and the worst was: 56.396s

loc supports more languages but I also believe it has more false positives. loc reporting seems nicer as well.

Pass the release flag when you build loc; `cargo build --release`.

I see ~5 seconds for loc and ~34 seconds for loccount to count a freshly cloned linux repository.

edit: woops, that was user time. These both spin all the cores. loc takes ~0.7 secs and loccount ~6.6 secs real time.

I'm not seeing any changes in my results. I'm testing in an old laptop, I guess that's why it's so slow.

My rustc version is 1.15.0 and go 1.8.

If you are running the program with `cargo run` that takes the same --release flag. Could be the machine difference though.

I'm not. Are you testing with go 1.8 btw?

Go 1.7.4 and rust 1.14. Interesting discrepancy in the relative speeds of the tools we are seeing.

Reply on news.ycombinator.com