Content deleted Content added
change to the new url |
|||
Line 45:
==Metrics==
The following aspects of each given implementation are measured:<ref>{{cite web|url=https://benchmarksgame-team.
* overall user runtime
* peak memory allocation
Line 55:
==Benchmark programs==
It was a design choice from the start to only include very simple toy problems, each providing a different kind of programming challenge.<ref>{{cite web|url=https://benchmarksgame-team.
This provides users of the Benchmark Game the opportunity to scrutinize the various implementations.<ref>{{cite web|url=https://benchmarksgame.alioth.debian.org/u64q/nbody-description.html#nbody|title=n-body description (64-bit Ubuntu quad core) - Computer Language Benchmarks Game|website=Benchmarksgame.alioth.debian.org|accessdate=13 December 2017}}</ref>
* [[Memory management#Dynamic memory allocation|binary-trees]]
Line 72:
==History==
The project was known as ''The Great Computer Language Shootout'' until 2007.<ref>{{cite web|url=https://benchmarksgame-team.
A port for Windows was maintained separately between 2002 and 2003.<ref>{{cite web|url=http://dada.perl.it/shootout/|title=The Great Win32 Computer Language Shootout|website=Dada.perl.it|accessdate=13 December 2017}}</ref>
Line 78:
The sources are kept in CVS, but it also has multiple forks on GitHub.<ref>{{cite web|url=https://github.com/Byron/benchmarksgame-cvs-mirror|title=benchmarksgame-cvs-mirror: A git mirror of the benchmarksgame cvs repository|first=Sebastian|last=Thiel|date=24 October 2017|publisher=[[GitHub]]|accessdate=13 December 2017}}</ref>
The project is continuously evolving. The list of supported programming languages is updated approximately once per annum, following market trends. Users can also submit improved solutions to any of the problems or suggest testing methodology refinement.<ref>{{cite web|url=https://benchmarksgame-team.
==Caveats==
| |||