2 ms·
For the vast majority of realtime tasks accuracy of a few tens of nanoseconds is fine, but random 50ms delays for GC aren't.
by learc83 7y ago
For the vast majority of realtime tasks accuracy of a few tens of nanoseconds is fine, but random 50ms delays for GC aren't.
- pjmlp 7y agoThat is why Java variants for embedded soft real time deployments have completely different kind of GC implementations like something as OpenJDK or IBM J9, and expose regions and access to unamaged memory. Likewise .NET's support for value types and low level programming also means not everything needs to be GC-allocated.
- learc83 7y agoThat's all true. But at some point if you really need to avoid GC, you end up writing in a subset of C# that is so limited, it's really just C. Most people don't have those kinds of performance considerations. I use C# for soft realtime all the time, but in the instances when I have done actual realtime embedded work, I just used C.