3 ms·

Having worked with real-time systems, it's far from being an urban legend. Please name "real-time" garbage collectors available for mainstream languages. And

Having worked with real-time systems, it's far from being an urban legend. Please name "real-time" garbage collectors available for mainstream languages. And note that I'm not talking about ability to serve soft real-time services where you're allowed between 1 to 5% of all transactions to miss their deadline. Do that for a car break system or for an airplane guidance system and lives are lost. Heck, do that for video decoding and frames are dropped.

nickpsecurity 10y ago
They make new ones on a regular basis with different properties. Most customers just buy the existing products from the commercial sector, though. Here's a few links to performance and embedded-oriented ones that support predictable pause times with one letting it go down to one, move instruction given pauses are interruptable. http://www.jopdesign.com/doc/nbgc.pdf http://www.jopdesign.com/doc/nbgc.pdf https://www.usenix.org/legacy/events/vee05/full_papers/p46-click.pdf https://www.usenix.org/legacy/events/vee05/full_papers/p46-c... http://www.cse.buffalo.edu/~lziarek/euro.pdf http://www.cse.buffalo.edu/~lziarek/euro.pdf http://www.aicas.com/papers/ismm02f-siebert.pdf http://www.aicas.com/papers/ismm02f-siebert.pdf So, there's some examples to work with. There's plenty more, too. Just search Google with terms "concurrent," "real-time," and "GC." Or "pauseless" replacing "concurrent." Or "hard" before "real-time." That combo is how I track them.