6 ms·
It's unfortunate "real-time" is getting so heavily overloaded. It used to mean "guaranteed bounded latency". "Real-time" is now being used for streaming APIs t
by naasking 7y ago
It's unfortunate "real-time" is getting so heavily overloaded. It used to mean "guaranteed bounded latency".
"Real-time" is now being used for streaming APIs to mean "small latency on average, but no guarantees".
- egeozcan 7y agoIs there a more correct marketing term for "small latency on average, but no guarantees"?
- deleted 7y ago[deleted]
- junke 7y agosoft real-time https://en.wikipedia.org/wiki/Real-time_computing#Criteria_for_real-time_computing https://en.wikipedia.org/wiki/Real-time_computing#Criteria_f...
- airstrike 7y agoSome might argue that is the default meaning of "real-time" these days Maybe you guys ought to call hard real-time "Guaranteed bounded latency" when needed.
- mrits 7y agoI agree. In my experience it now means anything that could be shown during a sales demo without needing intentional pauses.
- PudgePacket 7y agoI assumed they used the words "real time" in a patient monitoring sense to mean Doctors being able to monitor patient data without having to go between rooms themselves or wait for reports. Kind of how you'd say you have a dashboard for your business to see metrics in real time (as opposed to some kind of daily report). I think that usage of real time is very common outside of a pure engineering sense, so you're being a bit of a stickler by being annoyed at this specific instance ;)
- sergiotapia 7y agoWhen I learned about this stuff years ago with SignalR this was called soft real-time. My Phoenix channels, your rails action cable, your web sockets: soft real-time. Real-time was reserved for true real time guaranteed delivery times.
- cma 7y agoI always heard hard real time for that, and "real time" could refer to either and was often used when talking about game rendering, etc.
- lobotryas 7y agoI don’t see why you had to call him out. “REAL TIME” is also an engineering term with a strict definition. If You paid me for a real time stock ticker and you later found out it had a delay of a second or two you would want a refund.
- joshuak 7y agoAsking for a real time stock ticker is also not using "real time" as a term of art, having a 2 second delay in stock data might be a failure to deliver on application requirements, but it is not necessarily a failure to deliver a "real time" system if the 2 second delay is strictly reliable. The non strict usage is far more common then the term of art. One would be well advised not to assume "real time" is being used as a term of art unless specifically called out, or clear from the context. I'd say common usage of the phrase "real time," means with respect to human perception, and that is how its being used here.
- naasking 7y ago> I'd say common usage of the phrase "real time," means with respect to human perception, and that is how its being used here. So do you consider YouTube a real-time system? After all, images are moving on your screen "in real-time" from the user's perspective. It seems to me that these are all streaming systems, and when the data is "live", then it's "live streaming". Even colloquially, I hazard that "real-time" has some implication that there's some correspondance between your temporal reference frame and the original temporal reference frame. I think the engineering definition just made that correspondance precise.
- sb8244 7y agoI agree that this is soft real-time but think that the usage is pretty clear in the web world. I'm not sure it's a bad thing that is taken on a different meaning in a different context. I view real-time as "the clients reflect the true state of the world without taking action." So if something changed the state of the world, all clients paying attention to that should also be updated.
- naasking 7y ago> I view real-time as "the clients reflect the true state of the world without taking action." So if something changed the state of the world, all clients paying attention to that should also be updated. That's a perfect description of "live streaming".
- sb8244 7y agoWhich has completely different meaning in the web world. Context matters.
- naasking 7y agoNo it doesn't. It's literally the same thing: "soft" real-time streaming of data. Medical data in one case, moving images and audio in another. The properties are the same in either case, that's why the term fits.
- sb8244 7y agoMy point is that when you say real-time in the web world, you can assume "soft real-time" because of the context. You would use specific language like "hard real-time" if it was so. Saying context doesn't matter is just ignoring how everyone else uses language and saying that your view of it is right.
- naasking 7y agoI meant that "live streaming" doesn't have a different meaning in the web world. So now we have two terms referring to exactly the same thing, which doesn't resolve the term conflation problem I initially wrote about. The "web world" context isn't that different from the larger software engineering world that they should repurpose engineering terms. > Saying context doesn't matter is just ignoring how everyone else uses language and saying that your view of it is right. I am saying that web programmers do tend to use professional language wrong, that it's unfortunate, and that we should try to correct it when it happens. I don't think the first part is controversial, but apparently trying to insist on precise engineering terminology when talking about engineering systems is controversial.
- andi999 7y agoYes. Its actually terrible. This is an application where you want hard realtime. You dont want golang after 2-3 days of uptime to do some big GC and then the monitor finds out that the patient was in a critical state 5 minutes ago. Well the system is much better then nothing, but I hope they do a second iteration.
- onebot 7y ago5 minute stop-the-world garbage collection? Go has done quite a bit to improve garbage collection times. I don't honestly believe that it could get anywhere nearly as bad as you imply it to be.
- joshuak 7y agoI'm sure that this is just hyperbole, but I can't imagine this not being a perfectly reasonable context in which to deploy a go application. In my mind "real time" as a term of art applies to things like hardware control systems with very strict tolerances. Although, as a hacking challenge I'd love to see the most catastrophic delay one could plausibly accidentally code into a go application.
- kortex 7y agoDownvote because 5 minutes is absurd as a STW GC time, for ANY gc language. Heck, I wouldn't accept 5 minute lag in a python prototype. Even in the dewey eyed early years, Go saw STW latency in the hundreds of milliseconds. By 1.8 it's in the hundreds of microseconds. Your hard-real-time is out the window as soon as routing and UDP is involved. The intent is "real time bounded by the amount of time it would take doctors to react to a code blue (heart issue/failure". One second of reaction (thousands of gc's, dozens of health checks, a near eternity in program time) isn't going to make a difference when human reaction time latency is hundreds of milliseconds. Call it "live streaming" if that sounds more objective, but conceptually if the clients (humans) don't perceive a difference in state, it's real time (to them). Save the milliseconds-hard-real-time talk for rockets and cars. https://blog.golang.org/ismmkeynote https://blog.golang.org/ismmkeynote https://www.reddit.com/r/golang/comments/aetba6/gcs_stw_pauses_in_go112_beta_are_much_shorter/ https://www.reddit.com/r/golang/comments/aetba6/gcs_stw_paus...
- pgwhalen 7y agoThis comment always shows up and I find it strange. Surely engineers can realize that while "real-time computing" has a strict definition, the phrase "real-time" has much broader meaning and it bumps up against the software world very often.
- naasking 7y agoSure, but this is a engineered solution we're talking about. Don't you think it should use the engineering terminology? I'm not calling out this person specifically, I'm just hopeful that we can use more precise terms instead of overloading existing ones. I think "streaming API" or "live streaming" is a better fit for these purposes.
- fragmede 7y agoIf we're going to play that game, then "real time" may never have come to refer to the hard system guarantees as you think of them. The earliest computers didn't even include an operating system, never mind one with real time guarantees as we think of them today. You submitted your program on paper tape (later, punch card.) and hours later, you'd get the output. This was the batch computing era. The idea of getting a (soft) real time response from the computer (which was the size of a room), was unheard of. As computers evolved, real time systems came to refer to computers that operated on the opposite of batch computing. The user could interact with the system in "real time", rather than having to wait hours after submitting the job for the results. Later on came the distinction between systems with hard real time (vs soft) guarantees. Computers didn't have the same CPU speed that we have access to today, so even audio processing required special real time guarantees. Eventually, "hard real time" was shortened to "real time", which takes us to today. Systems which have existed since the dawn of computing such as banks back in the 50's, or the IRS, still hold onto the batch vs real time nomenclature, possibly because batch processing systems still exist. Banks still process records nightly in batches, some even still run on newer versions of the same IBM mainframes, though some are starting to move to "soft" real time systems. (If you ever wondered why it can takes days for a check or bank wire transfer to clear, this is why.)
- corporateslave5 7y agoIt’s more the case that your usage of the term is outdated, but you still complain that the world doesn’t conform to your understanding
- deleted 7y ago[deleted]
- bluebknight 7y agoThe real problem in speech is not precise language. The problem is clear language. The desire is to have the idea clearly communicated to the other person. It is only necessary to be precise when there is some doubt as to the meaning of a phrase, and then the precision should be put in the place where the doubt exists. It is really quite impossible to say anything with absolute precision, unless that thing is so abstracted from the real world as to not represent any real thing. Richard Feynman