News for hackers. Stuff that matters.
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.