How low can you go? Ultra low latency Java in the real world [video]

Re:How low can you go? Ultra low latency Java in the real wo... by bilbo0s on Friday December 21, 2018 @10:48AM (#18734008)

>In C++, memory allocation is slow, so you worry about memory allocation up front. In Java, GC is a pain so you worry about memory allocation up front...

This.

A lot of people seem to be willfully dismissive of this reality when they are fanboying for their favorite languages.

Ask for memory in C++, you'll take a HUGE hit getting it. Ask for memory in Java, and you'll get it lightning fast, but you'll take a huge hit getting rid of it. Either way, you should carefully plan memory usage up front.

Basically, one road leads to death and despair, the other leads to disease and destruction...

pray you choose wisely.

[ Parent | on HN ]

Re:How low can you go? Ultra low latency Java in the real wo... by gpderetta on Friday December 21, 2018 @11:23AM (#18734309)

Any moderately performance sensitive code in C++, assuming it needs allocations at all will use a dedicated allocator.

While it is hard to beat existing general purpose allocators in all the scenarios, it is easy for specific use cases.

[ Parent | on HN ]

Re:How low can you go? Ultra low latency Java in the real wo... by kjeetgill on Saturday December 22, 2018 @04:37AM (#18739847)

True but these approaches in both C++ and Java start to converge: Arena allocation vs Pooling/unsafe. The question is, how annoying is your performance insensitive code?

[ Parent | on HN ]