By javathreads
via java.sys-con.com
Published: Sep 17 2008 / 16:53
Faced with the demands of mission-critical applications, many enterprise developers have pushed the Java language and the Java Virtual Machine (JVM) to the limit. The most common issue seen in transactional environments is achieving predictable response time or latency – in other words, the time it takes the system to respond to a request or to move a transaction through the IT infrastructure. In such environments, Garbage Collection (GC) moves from being a valued feature to a major headache.
Comments
jtheory replied ago:
Interesting, but doesn't seem to actually match the title. He mentions financial applications in passing (without details) and something about programming a robotic arm, but that's it. It's super-important to understand that RT processing comes at the *cost* of significantly lower overall performance -- that's why (as the article explains) the RTSJ has tuning options for letting only the essential threads be realtime, and the rest not.
So I'd still like to read an article about how to decide when an application will actually benefit from realtime processing -- how to quantify the performance trade-off, etc. etc..
Umberto replied ago:
A typical use of RTSJ application can enable financial program trading systems to execute time-critical trades, meet rigorous timing requirements for mission-critical real-time applications without interruption from the Garbage Collector or other Interrupts, this is when you will benefit from Real-Time.
Read this one:
http://www.devx.com/Java/Article/35246
Voters For This Link (8)
Voters Against This Link (0)