News for hackers. Stuff that matters.
Re:Java’s new garbage collector promises low pause times on ... by eikenberry on Thursday August 30, 2018 @01:29PM (#17878712)
With those latency requirements why did you use Java?
Re:Java’s new garbage collector promises low pause times on ... by dnomad on Thursday August 30, 2018 @01:50PM (#17878924)
Plenty of people are writing low-latency trading applications in Java where the latency budget is under 100 microseconds. This has been the case for several years now.

It's by no means new or even especially difficult these days. The resulting code is far more maintainable and robust than C++ solutions.

Re:Java’s new garbage collector promises low pause times on ... by hermitdev on Thursday August 30, 2018 @04:30PM (#17880458)
I've had the opposite experience. For green-field applications, it's far easier to write the application in C++ than Java & meet the latency requirements. Java requires far too much tuning, where as C++, from the get go, you can generally just glance at the code and have a good idea of the latency.

We're currently fighting a Java app that in general has decent latency (10s of usecs), but has outliers of greater than a second when GC kicks in. We don't have that issue with the C++ components of our trading system.

Re:Java’s new garbage collector promises low pause times on ... by phakding on Thursday August 30, 2018 @09:15PM (#17882195)
It's always going to be subjective. If you have people experienced in gc tuning, it's pretty easy to weed those gc outliers out. I am currently doing that for one of the applications for the company I work for. For me, it would be far easier to write a low latency, high concurrency Java app than a c++ app. The last c++ app that I was asked to write works horribly and bleeds memory. But it was not an important app.
Re:Java’s new garbage collector promises low pause times on ... by ADefenestrator on Wednesday September 05, 2018 @12:33AM (#17915050)
Oof. There's probably some compounding factors that make it more difficult, but usually getting GC pauses <500ms isn't that hard with current-gen collectors. Either being very careful with CMS, or just feeding G1 a lot of memory.
Re:Java’s new garbage collector promises low pause times on ... by devonkim on Thursday August 30, 2018 @02:14PM (#17879197)
I’ve heard a pretty effective, lazy strategy for this scenario is to oversize the heap to avoid GCs through the trading day and to simply restart the application before the next day. Unsure if it’s viable for all trading platforms, but it makes sense for some I’m sure.
Re:Java’s new garbage collector promises low pause times on ... by hermitdev on Thursday August 30, 2018 @04:33PM (#17880484)
Depends on your order volume. Sure an oversized heap may work for low order volume, but if you're dealing with high volume, even hundreds of gigabytes of RAM isn't even for a trading day.

And yeah, we restart everyday (we only trade US equities, so plenty of downtime for a restart).

Re:Java’s new garbage collector promises low pause times on ... by phakding on Thursday August 30, 2018 @09:08PM (#17882164)
You would be surprised to know majority of trading companies/exchanges use Java for trading platform. So does majority of companies in finance sector. I have been working in this secor for over 10 years and have interviewed for many of them.
Re:Java’s new garbage collector promises low pause times on ... by pk3469 on Friday August 31, 2018 @12:24AM (#17882948)
I would be surprised. I was under the impression that kdb+ holds the majority role in fintech.