3 ms·
The division you are looking for is Hard Realtime: Embedded system, no virtual memory/OS. Or special OS provisions to let them run. Soft Realtime: Responsive.
by valarauca1 10y ago
The division you are looking for is
Hard Realtime: Embedded system, no virtual memory/OS. Or special OS provisions to let them run.
Soft Realtime: Responsive.
In the case you are aiming for the second. There are several million things that'll net greater performance. We're talking about saving a matter of nano-seconds in C/C++. How you load your config will have more effect then this.
If you want to save $1,000,000 rolling pennies a start. But there are likely way bigger savings elsewhere, worth way more time, and less effort.
- karmakaze 10y agoI didn't think how it's achieved matters to the classification which is by the consequence of missing a deadline according to good ol' Wikipedia: Hard – missing a deadline is a total system failure. Firm – infrequent deadline misses are tolerable, but may degrade the system's quality of service. The usefulness of a result is zero after its deadline. Soft – the usefulness of a result degrades after its deadline, thereby degrading the system's quality of service
- valarauca1 10y agoYour difference between soft/firm is an arbitrary decision made by a manager, not really a hard/fast If I can't meet this deadline my system is a total technical failure. You've created a false dichotomy.