Vitaliy Filippov b07c3cec4c | ||
---|---|---|
cpp-optimizations | ||
dotnet | ||
java-optimizations | ||
results | ||
LICENSE | ||
README.md | ||
primes-alt.java | ||
primes-alt.lua | ||
primes.cpp | ||
primes.d | ||
primes.dotnet | ||
primes.erl | ||
primes.go | ||
primes.java | ||
primes.js | ||
primes.lua | ||
primes.php | ||
primes.pl | ||
primes.py | ||
primes.rb | ||
primes.rs | ||
primes.swift | ||
run.sh |
README.md
langs-performance
C++ vs. Python vs. Perl vs. PHP vs. Java vs. NodeJS vs. Go vs. Ruby vs. Rust vs. Swift vs. D performance benchmark
Blog articles:
- 2016: https://blog.famzah.net/2016/09/10/cpp-vs-python-vs-php-vs-java-vs-others-performance-benchmark-2016-q3/
- 2016: https://blog.famzah.net/2016/02/09/cpp-vs-python-vs-perl-vs-php-performance-benchmark-2016/
- 2010-2012: https://blog.famzah.net/2010/07/01/cpp-vs-python-vs-perl-vs-php-performance-benchmark/
The benchmarks here do not try to be complete, as they are showing the performance of the languages in one aspect, and mainly: loops, dynamic arrays with numbers, basic math operations.
The times include the interpretation/parsing phase for each language, but it’s so small that its significance is negligible. The programs run for 90 wall-clock seconds and there are 6 identical runs, in order to have more reliable results. All scripts are using the very same algorithm to calculate the prime numbers in a given range. The correctness of the implementation is not so important, as we just want to check how fast the languages perform. The original Python algorithm was taken from http://www.daniweb.com/code/snippet216871.html.
Another similar project: https://benchmarksgame.alioth.debian.org/