3 ms·
Java: 1 minute 20 seconds. About a year later, testing a new JIT for Java, the Java time was down to 0.7 seconds I've been surprised at the speed of Java rece
by 10ren 18y ago
Java: 1 minute 20 seconds.
About a year later, testing a new JIT for Java, the Java time was down to 0.7 seconds
I've been surprised at the speed of Java recently. I wonder how much improvement is left in dynamic compilation.
The HP project Dynamo was an experimental JIT compiler where the bytecode format and the machine code format were of the same type; the system turned HPA-8000 machine code into HPA-8000 machine code. Counterintuitively, this resulted in speed ups, in some cases of 30% since doing this permitted optimisations at the machine code level. For example inlining code for better cache usage and optimizations of calls to dynamic libraries and many other run-time optimizations which conventional compilers are not able to attempt.
http://en.wikipedia.org/wiki/Just-in-time_compilation http://en.wikipedia.org/wiki/Just-in-time_compilation
- alecco 18y agoTime-space trade-off. Meaning Java uses a lot of memory for almost anything. Speed isn't everything.
- michaelneale 18y agoSometimes memory can cost speed as well. I find with java essentially you are amortising gains which are payed back with GC at a later date (in many cases I guess it is worth it). Its not one size fits all !
- pohl 18y agoThis sounds like it had less to do with Java and more to do with a large number of short-lived allocations in your design. A garbage collector can be abused in any language that has one.