Choosing Java instead of C++ for low-latency systems

Re:Choosing Java instead of C++ for low-latency systems by iexplainbtc on Monday February 22, 2021 @11:08AM (#26226106)

I don't understand all this confusion about what RT means, this is the definition of a RT system. If you can't complete the computation within the given deadline whatever partial result is discarded and the computation starts from scratch.

Decoding video and interactive rendering is a great example of an RT system. If you can't construct a frame within (usually) 16 ms you skip it and start with the next one.

[ Parent | on HN ]

Re:Choosing Java instead of C++ for low-latency systems by titzer on Monday February 22, 2021 @11:19AM (#26226254)

There is a difference between hard real time and soft real time. Hard real time systems mean that missing a single deadline may be a crash, whereas a soft real time system, missing a deadline just causes a degradation. Video is definitely soft real time.

[ Parent | on HN ]

Re:Choosing Java instead of C++ for low-latency systems by iexplainbtc on Thursday February 25, 2021 @08:43PM (#26270611)

Hard and soft real time depend entirely on the context. An example of hard real time is flight control. The whole sensor - actuator - decision process must happen within the given threshold.

[ Parent | on HN ]

Re:Choosing Java instead of C++ for low-latency systems by Spivak on Monday February 22, 2021 @11:18AM (#26226243)

But decoding video in practice isn't usually realtime because you still have to do it when you don't have kernel support and are at the whim of your kernel's scheduler which is basically always.

It's a good example of a problem where a realtime system would be useful but it's not a good example of a real-life realtime application (usually).

[ Parent | on HN ]