News for hackers. Stuff that matters.
Re:Java vs. Go performance by ghshephard on Friday April 24, 2015 @03:01AM (#9431794)
Once you heat up the JVM, Java can run like a bat out of hell. And, if you don't run into GC problems, it's as fast as anything out there.
Re:Java vs. Go performance by sacado2 on Friday April 24, 2015 @04:43AM (#9432077)
You can't fine-tune memory usage and can run into cache issues (or worse) if you deal with quite a lot of data, though.
Re:Java vs. Go performance by threeseed on Friday April 24, 2015 @05:26AM (#9432172)
Wait. What ? I have never seen any piece of technology with more tuning options than the JVM. Especially given how dramatically different your apps perform with different combinations. It's akin to old wifes tales about which settings to use when.

http://www.oracle.com/technetwork/articles/java/vmoptions-js...

And don't forget that much of big data is on the JVM e.g. Hadoop, Cassandra, HBase.

Re:Java vs. Go performance by lmm on Friday April 24, 2015 @05:05AM (#9432128)
> You can't fine-tune memory usage

What do you mean by that? There are some very fine-grained tuning options if you really need them.

Re:Java vs. Go performance by sacado2 on Tuesday April 28, 2015 @10:29AM (#9452595)
Maybe I'm wrong, but I don't know how you can say you want, say, a list of objects of class Foo be in contiguous slots of memory, rather than having a list of references to objects. Because the latter is very cache-unfriendly. In go, you can say whether you want a []Foo or a []*Foo
Re:Java vs. Go performance by lmm on Wednesday April 29, 2015 @03:14AM (#9456854)
You can do that "by hand" with buffers (and the HFT guys do) but yeah it's not easy or fun. C#-style struct types are supposedly coming in the next version.