What is “real time”?
The term “real time” is widely used nowadays. Although it is a technical term, it finds its way into quite normal conversation. I might be heard to say “I do not watch much real-time TV”, meaning that I use streaming services to watch what I want when I want. So, colloquially, real time means “immediate” or “occurring now”. How does this align with its precise meaning when we refer to a real time operating system, for example? …
Looking up “real-time system” in a rather old computer dictionary yields:
“Any system in which the processing of data input to the system to obtain a result occurs virtually simultaneously with the event generating that data.”
It cites airline booking systems being an example. This is clearly not a useful definition for our needs.
Here is a better definition:
“A real-time system is one in which the correctness of the computations not only depends upon the logical correctness of the computation but also upon the time at which the result is produced.If the timing constraints of the system are not met, system failure is said to have occurred.”
Another way of putting this definition is to say that a real time system is, above all, predictable. We tend to use the term deterministic.
So a deterministic operating system performs all its actions in a well defined timeframe and enables a programmer to produce applications with the same characteristic. Real time does not mean fast – it means fast [or possibly slow] enough for the specific requirements of the application in hand.
Unfortunately, it is not quite so black and white. An OS can have a degree of determinism – it is a question of the variance between the time taken to do operations under different circumstances. So, a classic real time operating system has a very low variance and is, hence, very deterministic. Linux, on the other hand, generally exhibits quite a high variance and may not normally be described as real time.
There is always the “brute force” approach to building a system, where you design with enough raw CPU power that the speed/variance of the OS hardly matters, as everything will be done in time. For some requirements, that might be a good solution, but, for many, such a profligate use of resources is not an option.
- Comments
- Write a Comment Select to add a comment
This is a great piece, Colin, thanks.
The term 'real-time' is especially overloaded in the database industry with so many so-called 'real-time database' offerings that really are streaming database systems or 'real fast' OLAP database systems. As a vendor that has the only actual real-time database system, it's been incredibly difficult getting through the noise to raise awareness of our product.
Indeed, equating "real fast" and "real time" is a problem. An interesting possible effect is that on our language: if we allow this equation to persist, we'll have no easy way to describe something that actually is "real time". [Rather like the way "unique" is often used to mean "very unusual"; we could end up with no way to express actual uniqueness.]
From back in the day: MicroProcessor Engineering Ltd - More Real, Less Time
:-)
To post reply to a comment, click on the 'reply' button attached to each comment. To post a new comment (not a reply to a comment) check out the 'Write a Comment' tab at the top of the comments.
Please login (on the right) if you already have an account on this platform.
Otherwise, please use this form to register (free) an join one of the largest online community for Electrical/Embedded/DSP/FPGA/ML engineers:
