Quote:
Originally Posted by 1075guy
its excessive horsepower has enabled teams to get sloppy with their coding, resulting in 100% cpu usage
|
I have a modest proposal: Can we use a phrase other than
"100% CPU usage" to describe the situation where the code is not meeting its deadlines?
Many well-designed safety critical systems use the CPU 100%: They have a low priority background task which uses all available CPU when none of the higher priority foreground tasks are running. So "100% CPU" is not necessarily a bad thing.
Perhaps the phrase "throughput margin" captures the intended meaning.
http://www.nasa.gov/centers/dryden/p...ain_H-1860.pdf
http://www.chiefdelphi.com/forums/sh...d.php?t=107733