Go to file
Vitaliy Filippov b07c3cec4c Same result format for primes-alt.java 2021-02-02 19:23:25 +03:00
cpp-optimizations Initial commit 2016-02-04 21:32:08 +02:00
dotnet Make the ".NET Core Linux" project files compatible with version 3.1.x 2019-12-27 18:18:23 +02:00
java-optimizations LinkedList info 2016-09-22 22:15:51 +03:00
results A quick benchmark redo for ".NET Core Linux" version 3.1.1 2019-12-27 18:23:32 +02:00
LICENSE Initial commit 2016-02-04 21:30:25 +02:00
README.md Port of the Python version to D 2018-01-27 15:55:24 +01:00
primes-alt.java Same result format for primes-alt.java 2021-02-02 19:23:25 +03:00
primes-alt.lua Add alternative Lua implementation without #arr 2021-02-02 19:19:15 +03:00
primes.cpp Print comparable results 2020-01-17 21:02:31 +03:00
primes.d Port of the Python version to D 2018-01-27 15:55:24 +01:00
primes.dotnet Symlink to the C# .NET Core implementation 2016-11-04 00:25:23 +02:00
primes.erl Add 2 more Erlang implementations. But shit anyway 2020-01-23 17:48:06 +03:00
primes.go Add lua + change cpp, js, rust and php, python, go to 30 iterations 2019-12-30 01:35:15 +03:00
primes.java Same result format for primes-alt.java 2021-02-02 19:23:25 +03:00
primes.js Print comparable results 2020-01-17 21:02:31 +03:00
primes.lua Print comparable results 2020-01-17 21:02:31 +03:00
primes.php Print comparable results 2020-01-17 21:02:31 +03:00
primes.pl Same format with perl 2020-01-23 02:07:47 +03:00
primes.py Print comparable results 2020-01-17 21:02:31 +03:00
primes.rb Limit running time by an ENV variable 2016-09-08 17:57:49 +03:00
primes.rs Same format with perl 2020-01-23 02:07:47 +03:00
primes.swift Minor refactoring, so that the code workflow is the same as the other languages 2018-01-12 12:23:12 +02:00
run.sh Port of the Python version to D 2018-01-27 15:55:24 +01:00

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:

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 its 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/