3 ms·

Actually the JVM is slow on startup. It has to decide if it's going to use the full Hotspot optimizer or something for shorter runs (Hotspot wont buy you anyth

Actually the JVM is slow on startup. It has to decide if it's going to use the full Hotspot optimizer or something for shorter runs (Hotspot wont buy you anything for a short-running app like e.g. cat'ing a file). Given that many phone apps are going to be started, looked at and shut down within a few seconds I don't think the comment is completely out of line.

ithkuil 16y ago
dalvik is different. for example dalvik bytecode can be adapted to match host endianness after being installed Running JVM bytecode which is designed to be big-endian (sparc was big-endian) requires some adaptation when executed (especially when constants are loaded from the constants pool) on little endian machines (x84), it seems that the JIT compiler takes care of it. However I don't know how much does this inpact on the JIT compilation speed. furthermore dalvik wasn't even a jit until android 2.2. I assume that this startup latency issue was taken into heavy consideration when designing the dalvik JIT, can anyone point to any resources about this?