"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken
What fun! Increase the Code multiplier! Ignore Memory! Zero out those benchmarks that push your favourite language to the bottom!
Which balance between Code-used and Time-used and Memory-used is best for you? Zero out those benchmarks which are unlike what your programs do!
Which is best for you?
Which balance between Code-used and Time-used and Memory-used is best for you?
Read "How not to lie with statistics: the correct way to summarize benchmark results" (pdf).
For each benchmark, B is the best measurement; for each language implementation, the best measurement L is then normalized to L/B
GM is the Weighted Geometric Mean of those L/B ratios.
missing : Language implementations with more than a couple of Timeouts (at the largest workload) distort the ranking - so they have been excluded. They can still be compared directly against another language implementation.
There are other ways to analyse and present this data: ask Which programming languages have the fastest programs? or look for patterns in Code-used Time-used Shapes or take the Summary Data and do your own analysis!
