Either someone did this on purpose or they have no idea how to write efficient Java code and benchmark it.
Either someone did this on purpose or they have no idea how to write efficient Java code and benchmark it.
[1] With good defined as fast. Many of the implementations there are so contorted that no one in their right mind would use anything like it in production. But they are fast.
— programs have to show the correct output
— program source code is shown
— programs can be contributed
What was the problem?
I said "Yep" as in "Yep, some people do contribute", and it has good implementations for some, while shitty ones for others, and it should not be taken way too seriously because of what he just said.
n-body Node js #6
https://benchmarksgame-team.pages.debian.net/benchmarksgame/... n-body Java #4
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...The benchmarks game does show measurements which take OSR and warm up into account —
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
"So we accept something intermediate between chaos and rigidity — enough flex & slop & play to allow for Haskell programs that are not just mechanically translated from Fortran; enough similarity in the basic workloads & tested results."
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...
What you describe is more like the "Are We Fast Yet?" project —
https://benchmarksgame-team.pages.debian.net/benchmarksgame/...