3 ms·
>> Imagine what software would be like if subroutines could start and end only at preset time intervals. “My subroutines all start at 3.68 millisecond intervals
by phkahler 10y ago
>> Imagine what software would be like if subroutines
could start and end only at preset time intervals. “My subroutines all start at 3.68 millisecond intervals; how
often do yours start?”
Mine start at 50 microsecond intervals. I've worked on stuff with shorter and longer intervals. Sometimes we have lists of tasks that need to run at different rates, so scheduling becomes a real pain. Welcome to the world of real time embedded software in high performance systems. The same thing applies, we make sure the worst case execution time is within the allowed intervals and use a master clock to sync everything up.
- jacquesm 10y agoI've done quite a few of these embedded systems with real time constraints and your summary is quite accurate. The good part for me is that once you have things nailed down they (usually, and if not then you're really in for a long night) don't shift and what works will continue to work reliably. This in contrast to non-real-time systems which tend to just freeze for random periods of time (sometimes seconds or even minutes) without any apparent cause. That's something that really puzzles me about todays software+hardware. In theory it should all be faster than ever but in practice I spend as much or even more time waiting for my computers than I ever did in the past. Maybe I'm just more impatient but I don't believe that's the reason here. Real time should be the norm, not the exception, just like encrypted communications should be the norm, not the exception. Computers should respond without noticeable latency to user input at all times.
- daveloyall 10y agoRemember moving your cursor through menu options in an NES game? (or using a 8-bit word processor?) Computers should be like that. Consumers shouldn't accept anything else. Responsive interfaces allow users to develop muscle memory. I used to type in complicated sequences of commands into my commodore 64 to perform common actions. (wow, I didn't know I wanted a $HOME with some scripts in it. Now I know!) When I'd make a typo in one of those sequences, it would commonly be quicker for me to reset the machine and start from the top. If I performed the same action twice (with a reset inbetween) and got a different result, I could logically conclude that I had a hardware problem. (Not every HW problem is permanent. Heat and grounding problems can both be fixed, unless some threshold is crossed...) Anyway, I figure that Wintel denied grandma that kind of computer because they learned from the hobbyists that neophyte users with quality hardware+software will exceed the creators in skill in less time than it takes to design the next gen rig--and a couple genius users will start building their own out of impatience! There's no profit in quality hardware+software combinations.
- deleted 10y ago[deleted]