Node.js 14 is over 20x faster than Python3.8 for fib(n)
1–10 of 119 posts
Re: Node.js 14 is over 20x faster than Python3.8 for fib(n)
#2An interpreter with a JIT is obviously faster than one without. Especially when dealing with CPU bound work.
I'm not sure this is entirely noteworthy unless you somehow think CPython has a JIT. Would be much more interesting to compare to pypy.
Re: Node.js 14 is over 20x faster than Python3.8 for fib(n)
#3I'm honestly not too surprised. I follow the v8 blog and they talk extensively about performance improvements on most releases.
Re: Node.js 14 is over 20x faster than Python3.8 for fib(n)
#4An interpreter with a JIT is obviously faster than one without. Especially when dealing with CPU bound work. I'm not sure this is entirely noteworthy unless you somehow think CPython has a JIT. Would be much more interesting to compare to pypy.
Indeed. Furthermore this basically just benches function call overhead by using the worst possible implementation of fib().
Function call is a well-known weak point of cpython, even amongst all its other weak points performance-wise.
It's hard to express how utterly uninteresting and useless TFA is, and if its author is surprised by the result… really the only component this tells us about is the author.
> Would be much more interesting to compare to pypy.
I'm not sure it is more interesting at all, let alone much more, but here are the results on my (obviously much slower than TFA's) machine:
> python3.9 --version
Python 3.9.1
> python3.9 fib.py
8555.904865264893 ms
> pypy37 --version
Python 3.7.9 (7e6e2bb30ac5fbdbd443619cae28c51d5c162a02, Jan 15 2021, 06:03:20)
[PyPy 7.3.3-beta0 with GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)]
> pypy37 fib.py
715.0719165802002 ms
> node --version
v14.15.4
> node fib.js
247.19056797027588 ms
Re: Node.js 14 is over 20x faster than Python3.8 for fib(n)
#5This is a pretty terrible implementation of fib(n).
Re: Node.js 14 is over 20x faster than Python3.8 for fib(n)
#6This is a pretty terrible implementation of fib(n).
It's a common approach to measuring function spawn cost.
Re: Node.js 14 is over 20x faster than Python3.8 for fib(n)
#7Doesn't the Node.js version use double precision floating point vs python using infinite precision integers ?
That would explain part of the difference in performance, and make the python version exact, but js version inexact.
Re: Node.js 14 is over 20x faster than Python3.8 for fib(n)
#8FYI: pypy3 is 10x faster than CPython on this benchmark.
~> python fib.py
4825.7598876953125 ms
~> pypy3 fib.py
514.7459506988525 msRe: Node.js 14 is over 20x faster than Python3.8 for fib(n)
#9An interpreter with a JIT is obviously faster than one without. Especially when dealing with CPU bound work. I'm not sure this is entirely noteworthy unless you somehow think CPython has a JIT. Would be much more interesting to compare to pypy.
Agreed. The speed difference between Node and Python is well known. v8 is one of the fastest things around. However, it's more than just JIT. There are business reasons behind why Node is so fast. The number of resources google has thrown against developing v8 means that pretty much nothing can surpass it in speed any time soon.
The fact this is on someones blog and posted to the front page means that a lot of people didn't know this. Well guess what, for you guys who don't know.... here's another fun fact: C++ is about 10x faster then node which makes it about 200x faster then python.
Re: Node.js 14 is over 20x faster than Python3.8 for fib(n)
#10An interpreter with a JIT is obviously faster than one without. Especially when dealing with CPU bound work. I'm not sure this is entirely noteworthy unless you somehow think CPython has a JIT. Would be much more interesting to compare to pypy.
How does the JIT compilation help in terms of CPU bound work? Is node somehow able to automatically parallelize this code? I know cpython is limited to a single core unless you specifically use multiprocessing. Or is this related to something else?