Editor: Julia is a dynamic programming language for technical computing known for its speed and performance. It’s like R, but less popular.
Julia vs Python
Should we ditch Python and other languages in favor of Julia for technical computing? That’s certainly a thought that comes to mind when one looks at the benchmarks on http://julialang.org/. Python and other high level languages are way behind in term of speed. The first question that came to my mind was different however: did the Julia team wrote Python benchmarks the best way for Python?
My take on this kind of cross language comparison is that the benchmarks should be defined by tasks to perform, then have language experts write the best code they can to perform these tasks. If the code is all written by one language team, then there is a risk that other languages aren’t used at best.
One thing the Julia team did right is to publish on github the code they used. In particular, the Python code can be found here.
A first look at this code confirms the bias I was afraid of. The code is written in a C style with heavy use of loops over arrays. This is not the best way to use Python.
I won’t blame the Julia team, as I have been guilty of the exact same bias. But I learned the hard lesson: loops on arrays should be avoided at almost any cost as they are really slow in Python, see Python is not C.
Given this bias towards C style, the interesting question (to me at least) is whether we can improve these benchmarks with a better use of Python and its tools?
Before I give the answer below, let me say that I am in no way trying to downplay Julia. It is certainly a language worth monitoring as it is further developed and improved. I just want to have a look at the Python side of things. Actually, I am using this as an excuse to explore various Python tools that can be used to make code run faster. Continue reading.
