3 ms·
> The initial benchmarks show something of a 2-9% performance improvement. You might be disappointed by this number, especially since this blog post has been ta
by eviks 3y ago
> The initial benchmarks show something of a 2-9% performance improvement. You might be disappointed by this number, especially since this blog post has been talking about assembly and machine code and nothing is faster than that right?
Indeed, reading the blog post build much higher expectations
- G3rn0ti 3y agoJust running machine code itself does not make a program magically faster. It‘s all about the amount of work the machine code is doing. For example, if the JIT compiler realizes the program is adding two integers it could potentially replace the code with two MOVs and a single ADD. However, what about the error handling in the case of an overflow? Python switches to its internal BigInt representation in this case and cannot rely on architecture specific instructions alone once the result gets too large to fit into a register. Modern programming languages are all about trading performance for convenience and that is what makes them slow — not because they are running an interpreter and not compiling to machine code.
- deleted 3y ago[deleted]