|
|
Log in / Subscribe / Register

A realtime developer's checklist

A realtime developer's checklist

Posted Nov 18, 2020 19:27 UTC (Wed) by hummassa (guest, #307)
In reply to: A realtime developer's checklist by meyert
Parent article: A realtime developer's checklist

Videoconference applications.
VoIP (voice over Internet Protocol)
Online gaming.
Community storage solutions.
Some e-commerce transactions.
Chatting.
IM (instant messaging)


to post comments

A realtime developer's checklist

Posted Nov 19, 2020 13:04 UTC (Thu) by mathstuf (subscriber, #69389) [Link] (2 responses)

Is instant messaging typically RT? Wouldn't the typing latency be the highest thing? Or is this more about "Typing…" notifications? Things interacting with hardware (vsync, constant FPS targets, machine controllers) or wetware deadlines (audio processing, audio/video sync) certainly make sense, but I would have thought typing would have interfered too much. Though if it is, it's almost certainly got longer deadlines than other use cases(?).

Note, I don't do RT development myself, so any misconceptions or naivete is certainly on my side :) .

A realtime developer's checklist

Posted Nov 19, 2020 14:03 UTC (Thu) by hummassa (guest, #307) [Link] (1 responses)

WRT RT, it's not the length of the deadline, but its predictability :-)

A realtime developer's checklist

Posted Nov 19, 2020 18:56 UTC (Thu) by glenn (subscriber, #102223) [Link]

Yes, it's more about predictability than latency, but optimizing latency can improve predictability (or allows one to achieve predictability on less powerful hardware).

Paul McKenney has a great paper on this: "Real Time" vs "Real Fast": How to Choose?".


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds