Content deleted Content added
mNo edit summary |
→Metrics: Adding/removing wikilink(s) |
||
Line 47:
==Metrics==
The following aspects of each given implementation are measured:<ref>{{cite web|url=https://benchmarksgame-team.pages.debian.net/benchmarksgame/how-programs-are-measured.html|title=How programs are measured - The Computer Language Benchmarks Game|website=benchmarksgame-team.pages.debian.net/benchmarksgame/|accessdate=29 May 2018}}</ref>
* overall user [[Run_time_(program_lifecycle_phase)|runtime]]
* peak [[memory allocation]]
* [[gzip]]'ped size of the solution's source code
* sum of total CPU time over all [[threads]]
* individual CPU [[utilization]]
It is common to see multiple solutions in the same programming language for the same problem. This highlights that within the bounds of a given language, a solution can be given which is either of high abstraction, is memory efficiency, fast, or parallelizes better.
|