Questions tagged [firm-real-time]

A classification of real-time where infrequent deadline misses are tolerable, but may degrade system quality, and a result received after its deadline is considered not useful.

From the real-time computing wikipedia page:

Firm: Infrequent deadline misses are tolerable, but may degrade the system's quality of service. The usefulness of a result is zero after its deadline.

An example might be a system that serves glasses of milk. If the system serves milk after its expiration date, the serving is useless. However, eating cereal without milk is tolerable, but not desirable.

3 questions
123
votes
12 answers

Differences between hard real-time, soft real-time, and firm real-time?

I have read the definitions for the different notions of real-time, and the examples provided for hard and soft real-time systems make sense to me. But, there is no real explanation or example of a firm real-time system. According to the link…
jxh
  • 69,070
  • 8
  • 110
  • 193
31
votes
6 answers

What are trade offs for "busy wait" vs "sleep"?

This is an extension to my previous question How does blocking mode in unix/linux sockets works? What I gather from Internet now, all the process invoking blocking calls, are put to sleep until the scheduler finds the reasons to unblock it. The…
Vivek Sharma
  • 3,794
  • 7
  • 38
  • 48
3
votes
0 answers

Concurrency framework for maximum throughput in real-time system

I'm working with a "firm" real-time system (the result will be unuseful if served after the deadline) which requires maximum throughput and robustness to load. More details about our system, we are processing telecommunication messages. The messages…
Nova
  • 186
  • 2
  • 5