← Back to context Comment by ch4s3 10 hours ago It’s pretty hard to make things like math faster for real world use cases in a bytecode interpreter. 4 comments ch4s3 Reply dmpk2k 10 hours ago It's a JIT nowadays. Admittedly an extremely simple one, to minimize compile times and maintenance overhead.You can get substantial performance improvements by using guards though. See what Wings3D does with is_float() everywhere in hot numeric-heavy code. dnautics 8 hours ago i ran a quick experiment where instead of doing boxing the way its done in the beam currently, i used a different boxing (NaN strategy and there was a 10x speedup ch4s3 4 hours ago Is that translates to real workloads you should open a pr. jimbokun 10 hours ago Java and Javascript run times do really well at that.
dmpk2k 10 hours ago It's a JIT nowadays. Admittedly an extremely simple one, to minimize compile times and maintenance overhead.You can get substantial performance improvements by using guards though. See what Wings3D does with is_float() everywhere in hot numeric-heavy code.
dnautics 8 hours ago i ran a quick experiment where instead of doing boxing the way its done in the beam currently, i used a different boxing (NaN strategy and there was a 10x speedup ch4s3 4 hours ago Is that translates to real workloads you should open a pr.
It's a JIT nowadays. Admittedly an extremely simple one, to minimize compile times and maintenance overhead.
You can get substantial performance improvements by using guards though. See what Wings3D does with is_float() everywhere in hot numeric-heavy code.
i ran a quick experiment where instead of doing boxing the way its done in the beam currently, i used a different boxing (NaN strategy and there was a 10x speedup
Is that translates to real workloads you should open a pr.
Java and Javascript run times do really well at that.