Code-used Time-used Shapes [19 Dec 2009 u32q]
Scatter plots of ↓ normalized Code-used and normalized Time-used measurements give shape to each language implementation and position the programs in a broader context. From concise at the left to less-concise at the right, from slower at the top to faster at the bottom.
Also, click a scatter plot to compare that language implementations directly - one-against-another for all the benchmarks - on Time-used, Memory-used and Code-used.
| | |||
| | |||
| | | ||
| | | ||
| | |||
| | | ||
| | |||
| | |||
| | | | |
| | |||
| | |||
| | |||
| | |||
| | | ||
| | | ||
| | | ||
| | | ||
| | |||
| | |||
| | |||
| | |||
| |
about Code-used Time-used Shapes
Measurements are normalized to the gzip Code-used of the smallest program and to the Time-used by the fastest program respectively. The scatter plots are given more shape by joining each data point to a median point.
Both axes use logarithmic scaling to show the full range of measurements, although there's at least two orders of magnitude more difference between program Time-used than program Code-used.
Thanks to Guillaume Marceau for demonstrating there was interest in this kind of presentation.
There are other ways to analyse and present this data: ask Which languages are fastest? or Which language is best? or take the Summary Data and do your own analysis!