3 ms·

That’s not an option, that was the whole point of the discussion.

• pron 9y ago
  If changing the JVM spec is an option, then surely so is using an existing spec. IBM has an RTSJ JVM[1], which, I believe, is based on J9. [1]: https://www.ibm.com/support/knowledgecenter/en/SSSTCZ_3.0.0/com.ibm.wrt.rtlinux.doc.30/homepage/plugin-homepage-rt.html https://www.ibm.com/support/knowledgecenter/en/SSSTCZ_3.0.0/...
  • kuschku 9y ago
    Changing the JVM spec has a chance at being applied in future normal JVMs. Using an entirely separate solution has not.
    • pron 9y ago
      It's not an entirely separate solution, but a Java standard. In any event, it's probably overkill if all you need are acceptable pause-times for games (RTSJ is for hard-realtime, safety-critical systems, where even 2us jitter may kill someone). There are "pauseless" GCs for the JVM (with 1-10ms max pause, depending on the GC) without hard realtime guarantees. We just need more free implementations.
      • mstoodle 9y ago
        Eclipse OpenJ9's -Xgcpolicy:metronome is one of those GCs. Depending on how you well you configure your operating system, it defaults to 3ms pauses along with an application utilization contract.