Live data from Hacker News

New Computer Language Benchmarks Game metric: time + source code size

benchmarksgame-team.pages.debian.net

41–50 of 59 posts

Re: New Computer Language Benchmarks Game metric: time + source code size

#41
post #15

I really wish they aggregated the metric of build time (+ whatever). That is a huge metric I care about. You can figure out it somewhat by clicking on each language benchmark but it is not aggregated. BTW as biased guy in the Java world I can tell you this is one area Java is actually mostly the winner even beating out many scripting languages apparently.

Do Java "build time" measurements include class loading and JIT compilation? :-)

Re: New Computer Language Benchmarks Game metric: time + source code size

#42
post #23

Earlier quoted context omitted.

> … basic statistics like… median, quartiles https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Could you guide me to the ones I mentioned, I'm not seeing them.

The linked page has box and whisker plots. On a box and whisker plot the lower bar is the min, the upper bar is the max. The box goes from 25th percentile to 75th percentile while the bar in the middle of the box is the 50th percentile.

Therefore the stats you mentioned are all there min, max, and average with two different definitions of average given (geometric mean, and 50th percentile).

Re: New Computer Language Benchmarks Game metric: time + source code size

#43
post #29

Earlier quoted context omitted.

Could you guide me to the ones I mentioned, I'm not seeing them.

The bar in the middle of the box is an "average" - the median. https://www.merriam-webster.com/dictionary/average https://www.itl.nist.gov/div898/handbook/eda/section3/boxplo...

It would be nice to be able to see the numbers in a table (perhaps in a auxiliary page, instead of the main page). Sometimes people want to rearrange the data or use another representation. (log scale? sort by 75% quartile? ...)

Re: New Computer Language Benchmarks Game metric: time + source code size

#44
post #29

Earlier quoted context omitted.

The bar in the middle of the box is an "average" - the median. https://www.merriam-webster.com/dictionary/average https://www.itl.nist.gov/div898/handbook/eda/section3/boxplo...

It would be nice to be able to see the numbers in a table (perhaps in a auxiliary page, instead of the main page). Sometimes people want to rearrange the data or use another representation. (log scale? sort by 75% quartile? ...)

For people who want to rearrange the data or use another representation, there are data files —

https://salsa.debian.org/benchmarksgame-team/benchmarksgame/...

Re: New Computer Language Benchmarks Game metric: time + source code size

#45
post #26

Earlier quoted context omitted.

All of the languages now have that trash in them. I'd like a "naive" benchmarks game where you write the code straight forwardly in a normal style for the language.

"simple" (2nd link on the homepage.) https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

Is that only for the mandelbrot benchmark?

Re: New Computer Language Benchmarks Game metric: time + source code size

#47
post #38
post #26

Earlier quoted context omitted.

"simple" (2nd link on the homepage.) https://benchmarksgame-team.pages.debian.net/benchmarksgame/...

>Java: 40 seconds >Python 3: 1h 09 minutes Well damn.

Not hard to do, I once took some C code, naively converted it to python [0] and it took hours instead of seconds to run.

[0] I wanted to output an image and the C code only ran statistics so I would have had to figure out some random C image library which wasn’t how I wanted to spend my day.

Re: New Computer Language Benchmarks Game metric: time + source code size

#50

Geometric mean of (time + gzipped source code size in bytes) seems statistically wrong. What if you shifted time to nanoseconds ? Or source code size in terms of Megabytes. The rankings could change. The culprit is the '+' I would think Geometric mean of (time x gzipped source code size) is the correct way to compare languages together. It would not matter what the units of time or size are in that case. [Here the ge…

I think the summed numbers might be unitless. At least all the other numbers are relative to the fastest/smallest entry. That is, what would make sense is score(x) = time(x) / time(fastest) + size(x) / size(smallest) instead of score(x) = (time(x) + size(x)) / score(best)
Post reply on HN