| ▲ | zwnow 4 hours ago | ||||||||||||||||
Realtime in tech is considered in timespans with short delays allowed, last time i have read about it it was like 100ms. | |||||||||||||||||
| ▲ | anonymousiam 3 hours ago | parent | next [-] | ||||||||||||||||
Heh. I wasn't aware that there was a new definition of realtime. My 40+ year career consisted of about 20% realtime embedded firmware development. In all of my experience, 100ms is an absurdly long delay. Most RTOSs (that call themselves such) have latency measured in μs. The last serious RTOS that I wrote (MSP430, non-preemptive) had a firm requirement that any task must complete within 1ms. That one ran on a single threaded MCU clocked at 25MHz. It had a unix-like scheduler, with prioritized tasks, and I even threw in a 'top' display that showed per-task MCU usage, and load average. | |||||||||||||||||
| |||||||||||||||||
| ▲ | foul an hour ago | parent | prev | next [-] | ||||||||||||||||
Are you talking about (very good) webapps? Your average RT software has an average of 10 to 30 ms delay between operations. Performs tasks in the order of nanoseconds. | |||||||||||||||||
| ▲ | fragmede 4 hours ago | parent | prev [-] | ||||||||||||||||
Realtime in tech has a specific definition. The Wikipedia article covers it in more detail, but think about things like airplane wing control or space rocket computers needing to do things exactly when asked, or else people die. | |||||||||||||||||
| |||||||||||||||||