What is and how does an RTA work?

Asked

Viewed 908 times

5

I recently read some questions about RTA and noticed there are not many explanations about it. Looking a little deeper into this subject I came across some conceptual questions, nothing about coding.

A real-time application (RTA) is an application program that works within a period of time that the user perceives as immediate or current. Latency shall be less than a defined value, usually measured in seconds.

  1. What qualifies an app to be an RTA or not? Your time execution?
  2. A RTA requires a certain hardware platform to work?
  3. What would be the method of development oriented (objects, models, tests, behavior) best suited to create an RTA?
  4. For general platforms, there are methods/languages more indicated(as) optimising the performance of the application?
  5. What is the latency rate implication in an RTA?
  • If your question does not depend on the language considered, use the tag [tag:language-independent], but do not add all possible.

  • Okay, thanks for the suggestion

1 answer

3


What qualifies an application to be an RTA or not? Its runtime?

I don’t like this idea of real-time application. An application can have parts in real time and parts that aren’t. If there is any part that is not then the application is not real time, but that means nothing. Specific routines would need to be in real time.

On specific points it is necessary for the response to take place with a fixed maximum time. It is not a question of being fast or slow, it is being guaranteed that it does not take longer than that. Of course it is common that the measures are low.

A RTA requires a certain hardware platform to work?

Not necessarily, but there are platforms that can be difficult to maintain real time. And there are some that facilitate.

What would be the most suitable development method (objects, models, tests, behavior) to create an RTA?

This is all nonsense, you’re looking at the wrong things. None of this has to do with real team. What happens is that very complex applications with a lot of abstraction becomes more complicated to analyze whether the guarantees will be fulfilled.

For general platforms, there are more suitable methods/languages(as) that optimize application performance?

It has certain languages that imposes use of a Garbage Collector or other mechanisms that may make execution times unpredictable, which makes it impossible to provide the necessary guarantees. It might still be possible, but it’s gonna take so much work, it doesn’t pay to use that language. So people usually use more C, C++, Ada, Rust, and languages like that. Even these cannot guarantee real time, they just create fewer difficulties.

Other than that nothing specific in languages mainstream.

It has operating systems that help RT, others make it difficult.

What is the latency rate implication in an RTA?

When the latency exceeds the established limit an opportunity is lost that could not. It can be:

  • one frame of a game that delays rendering and impairs gameplay
  • a stock market control and similar that ends up accidentally privileging one operation at the expense of another that went through application delay
  • a simulation that produces distorted results
  • an airplane control that slows down and causes an unsolicited accident outside the time it would need
  • that does not catch an error that can only be identified in a moment or still create a running condition that would not happen if time were respected
  • that creates a disruption in something that needs to maintain a linear sequence.

These are some among countless examples.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.