5 ms·
250ms is not real-time, nor high frequency.
by iphorde 6y ago
250ms is not real-time, nor high frequency.
- pjmlp 6y agoIt might not be high frequency, but it certainly is real-time, unless you are implying that the agencies that give this kind of government certifications are all a bunch of fools.
- eru 6y agoDoesn't real time just mean that you can guarantee to react within certain time limits? In principle, those time limits could be hours or days..
- pjmlp 6y agoYes, but those limits are part of certification processes like those done by companies like https://www.highintegritysystems.com https://www.highintegritysystems.com. Usually playing with numbers in these kind of deployments isn't part of the package.
- sam_bristow 6y ago250ms could easily be real time in the context of a given system. Real time doesn't (necessarily) mean fast, it means the latency is bounded.
- lmilcin 6y agoPlease, get informed on what real-time is before you comment (in general it is good idea to understand a concept before you place confident comments like yours). https://en.wikipedia.org/wiki/Real-time_computing https://en.wikipedia.org/wiki/Real-time_computing Real-time has nothing to do with performance and everything to do with predictability and deadlines. People are put off when they find out that real time versions of Java or Linux are actually slower than the regular ones. Until you think about it a little bit and if they were faster there would not be multiple versions. Real-time versions of products are created because sometimes performance is achieved by means of stochastic processes or amortizing costs and you need to remove these optimizations to be able to support deadlines. Real-time programming emphasizes ability to calculate how long an operation will take as more valuable than raw performance.