Re:JEP 295: Ahead-of-Time Compilation
by OldSchoolJohnny on Thursday October 27, 2016 @04:51PM
(#12809961)
I'm surprised to hear anyone running Java in the trading industry. Isn't speed a huge factor in that industry?
[ Parent
| on HN ]
Re:JEP 295: Ahead-of-Time Compilation
by eternalban on Thursday October 27, 2016 @05:15PM
(#12810245)
> Isn't speed a huge factor in that industry?
Exactly. There are a lot of high performance system written in Java. For long running systems, the startup cost is irrelevant. And for networked systems (such as fintech) you are going to be IO bound. The main issue as far as Java and high performance is the GC related pauses and that is a concern shared with any GC'd runtime.
And for Java it's actually much less of an issue thanks to the crazy manhours put into developing fast GC for Java. I suspect Azul Systems's pauseless GC is probably quite popular in HFT.
Re:JEP 295: Ahead-of-Time Compilation
by brianwawok on Friday October 28, 2016 @12:20PM
(#12817642)
They are trying to sell it for sure. They attend a lot of events.
I am not aware of any trading company using it. May be some.. but the high perf people I know go other ways.
The JVM is super speedy, if you can mitigate startup time and the time required to warm up the JIT.
Re:JEP 295: Ahead-of-Time Compilation
by lomnakkus on Thursday October 27, 2016 @05:16PM
(#12810256)
... and Distruptor/Aeron. (etc.)
You're assuming Java is slow. Evidence suggests otherwise. Eg. LMAX Exchange uses a lock-free ringbuffer they call Disruptor [1] which enables 6M tps on a single thread [2]
[1] https://lmax-exchange.github.io/disruptor/ [2] http://martinfowler.com/articles/lmax.html
Re:JEP 295: Ahead-of-Time Compilation
by brianwawok on Friday October 28, 2016 @12:23PM
(#12817678)
And disruptor is a few years old now, there is a whole new wave of queues with even better performance.
I seem to recall a prior discussion where a dev working on HFT stuff said that speed is a huge factor, but so is the ability to rapidly change functionality. They settled on Java because it was fast enough (HFT would have to be IO bound, right?) while still being flexible enough to allow them to adapt to daily changes in requirements.
Besides what the others already replied, the use in the trade industry is one of the reasons of Java having to adopt AOT, value types, JNI replacement and better integration with GPGPUs.
Re:JEP 295: Ahead-of-Time Compilation
by chrisseaton on Thursday October 27, 2016 @07:14PM
(#12811303)
For example:
Thus the Java.
Java shot itself in the foot with the whole GC thing. Then it built a gigantic robot exoskeleton called Hotspot to help itself walk fast again.
Re:JEP 295: Ahead-of-Time Compilation
by lucian1900 on Friday October 28, 2016 @06:58AM
(#12814682)
Java's GC isn't why it can be slower than C/C++ and the JIT (HotSpot) has nothing to do with the GC.