Better Embedded System Software by Koopman Philip

Author:Koopman, Philip [Koopman, Philip]
Language: eng
Format: epub
Published: 2021-02-01T16:00:00+00:00

18.1.2. Possible symptoms

Measurements of memory, CPU, network bandwidth, or other hardware capacities are above 75% to 85% full. (The number depends on your situation; in some cases above 50% full can be an issue for an especially long-lived and change-prone system.)

The system sometimes misses real time deadlines or runs out of memory at run time.

Some combinations of features can’t be turned on at the same time due to insufficient computing power, memory, or network bandwidth.

Developers are spending a significant amount of time optimizing the system to meet resource constraints. Examples include making code faster, making code smaller, compacting data structures (e.g. , using bit fields instead of bytes to store Boolean variables), or combining network messages to reduce bandwidth use. A particularly risky manifestation of this is when an ad hoc, complex real time schedule is created to compensate for lack of processing power (see Chapter 14. Real Time ).

Design guidelines are being violated for the sake of speed or size optimization (e.g. , goto statements or jumps are used solely to reduce code size).

Assembly language is being used instead of a higher level language such as C or C++.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.