JVM JIT optimization techniques

Re:JVM JIT optimization techniques by userbinator on Sunday May 29, 2016 @12:28AM (#11794785)

It's interesting that the "gz" column, which reflects the amount of source code required, shows a very slight trend towards C being smaller, although there are big exceptions like regex-dna and reverse-complement.

I'm not seeing the 400x more memory - there is a 40x though. But if you add up the columns for the programs that have both C and Java versions, you get this rough summary...

           secs    KB       gz
    Java   76.33   2004048  12775
    C gcc  37.32   793652   11651

...that Java is on average half as fast as C and uses 2.5x more memory, while requiring slightly more source code.

[ Parent | on HN ]

Re:JVM JIT optimization techniques by igouy on Friday June 03, 2016 @11:25AM (#11830846)

>> more memory

http://programmers.stackexchange.com/a/189552/4334

[ Parent | on HN ]

Re:JVM JIT optimization techniques by pvg on Sunday May 29, 2016 @05:12AM (#11795619)

"half as fast as C and 2.5x the memory on average" is a stupendously good result for any managed runtime. Most don't get anywhere near it while providing more than acceptable performance in practice.

[ Parent | on HN ]

Re:JVM JIT optimization techniques by MrBuddyCasino on Sunday May 29, 2016 @01:00PM (#11797079)

Yes, and 2.5x is something that can be dealt with by deploying beefier hardware. The productivity gain is what makes that tradeoff a no-brainer.

[ Parent | on HN ]