3 ms·
Interesting for sure, but that's definitely a more painful optimisation journey than the Rust one, which only involved Rust. No custom JITing of a subset of Rus
by IshKebab 3y ago
Interesting for sure, but that's definitely a more painful optimisation journey than the Rust one, which only involved Rust. No custom JITing of a subset of Rust, or calling out to C.
I think the real takeaway from my experience of Rust vs Python performance is that in practice people don't optimise 99% of Python so the real number of significance is the 8x speedup he got from just switching to Rust with no profiling whatsoever.
That's actually quite a low difference compared to my experience - I'd say 50x is more typical.
- pjmlp 3y agoIt would be a different matter if something like PyPy would be the reference implementation, but alas we are quite far from it. As it stands, any AOT/JIT compiled language has an edge over Python, considering using only the reference implementation, which is quite relevant on systems were one cannot expect to allowed to install additional development tools. As for the bindings to native libraries, yeah Python might be favoured for bindings, however those native libraries can be called by any language that has FFI capabilities anyway, alongside their JIT/AOT capabilities.