The benchmarking itself was done in a simple and
fairly un-scientific fashion.
... older Pentium IV workstation. Run-times were
measured using wall-clock time.
but still a good read about tweaking c++ (I think at the time, clang and gcc were still implementing the C++11 standard features).
This is really old. C++, Java are mature languages. Scala hit 2.11 in March 2014, while Go version 1 was released in March 2012 and currently is at 1.3. Versions don't tell the whole story, but they do matter.
16 comments
[ 4.1 ms ] story [ 15.4 ms ] threadhttp://research.google.com/pubs/pub37122.html
Venue : Proceedings of Scala Days 2011
Publication Year: 2011
Submitters: please use an article's title unless it is linkbait or misleading [2].
1. Submitted title was "Google Publishes C++, Go, Java and Scala Performance Benchmarks"
2. https://news.ycombinator.com/newsguidelines.html
The algorithm encoded in the benchmark is loop recognition, but the purpose of the paper is to benchmark the languages, not to find loops.
this is the real artical, which just points to the pdf
Also i remember long HN threads about this in mid 2011 but i can't find them, here'a a later discussion https://news.ycombinator.com/item?id=4539668
http://blog.golang.org/profiling-go-programs
I guess they forgot about C++11's auto?
https://news.ycombinator.com/item?id=2615096