Bug#782171: Benchmark of linux and chromium

[Matthieu Caneill <matt@brokenwa.re>]

Hey,

On Wed, Apr 06, 2016 at 07:37:53AM +0200, Orestis Ioannou wrote:
> (I had to run latest cloc from github because the one in testing has an
> older release that affects chromium :D )

That point makes me feel pretty confident that cloc can be broken for
other packages. It would be relevant to carefully log errors when we
run the plugin on the whole archive!

> - time cloc-1.66.pl --by-file-by-lang -csv linux-4.4.6
> 
> files,language,blank,comment,code
> 22558,C,2217923,2064183,11330129

That is awesome to have the comments, it adds a good value IMO. Can't
wait to query debsources, asking which license is the most popular
among non-commented code, and other funny queries :)

> 159.95s user 
> 21.10s system 
> 81% cpu 
> 3:40.93 total

That's significantly slower than sloccount, but well, looks ok for
something as big as the linux package. Have you had the chance to see
if it parallelizes well?

> 14,Ruby,59,81,309
> 8,vim script,75,112,264
> 2,Racket,17,51,255
> 4,DTD,44,166,245
> 1,Korn Shell,39,46,223
> 4,XAML,30,50,90
> 4,Standard ML,9,0,61
> 4,Groovy,17,96,57
> 4,PHP,9,0,54
> 9,Verilog-SystemVerilog,0,0,52
> 4,sed,12,21,38
> 1,R,5,5,37
> 1,Prolog,1,-1,32
> 1,Swift,2,0,7

... is that even true? That's off-topic now, but I'm looking forward
to see in which files of chromium we can find php and ML :)

Thanks for you work on this bug!
Cheers,
--
Matthieu