3 ms·
Was a specialized real-time JVM used for this? I know real time isn't necessarily low latency, but it sounds like both are desired properties in this sort of s
by bigbubba 6y ago
Was a specialized real-time JVM used for this? I know real time isn't necessarily low latency, but it sounds like both are desired properties in this sort of situation.
- junon 6y agoRealtime and low latency are two different properties. Realtime systems have timing concerns and can oftentimes be slower than non-realtime systems.
- lmilcin 6y agoThis is not strictly true. Realtime means processing of at least some of the events and tasks in your application must be completed before a set deadline. For example, coin acceptor that detects what kind of coin you dropped in has x milliseconds to figure out if the coin is to be accepted or not. If it can't do it within the time you get unhappy customer. Realtime systems don't have to be very performant, but they don't have something like 99th percentile latency shooting up. All events must be processed within deadline. Low latency systems are soft realtime PLUS performance. In a low latency trading system you have to respond to market within a deadline to have a chance to do something useful but if you don't normally it doesn't mean lives are lost, metal is bent, etc.
- iphorde 6y agoRealtime requires low-latency. In trading, they require real-time, not low-latency.
- peter_lawrey 6y agoSome people use Azul Zing but we typically use OpenJDK or Oracle JDK.