3 ms·
If you ever try to write a bash script that calls a Java program in a tight loop, you'll know the limitations of a fat interpreting runtime with JIT compilation
by haxen 6y ago
If you ever try to write a bash script that calls a Java program in a tight loop, you'll know the limitations of a fat interpreting runtime with JIT compilation. Another relevant use case is the Stateless Lambda server-side architecture.
- MaxBarraclough 6y agoI believe Java (OpenJDK at least) is slow to start even if you disable the JIT and go with pure interpretation, and even if you disable runtime bytecode verification. It's just generally heavyweight and slow to get off the ground. I imagine JIT compilation should help with this, as you suggest.
- deleted 6y ago[deleted]
- MaxBarraclough 6y agoOops, too late to edit, but I meant ahead-of-time compilation should help with this
- deleted 6y ago[deleted]