And Elliot Saba writes: > The first thing you should do is run your code once to warm up the > JIT, and then run it again to measure the actual run time, rather > than compile time + run time.
To be fair, he seems to be timing MATLAB in the same way, so he's comparing systems appropriately at that level. It's just the tuned BLAS+LAPACK & fftw v. the default ones. This is one reason why MATLAB bundles so much. (Another reason being the differences in numerical results causing support calls. Took a long time before MATLAB gave in to per-platform-tuned libraries.)
