Part 13: Example 3 (Maximizing Idle Periods) - Batch I/O requests
Frequent I/O operations represent another pitfall in programming for energy efficiency. Frequent, small reads and writes generate a chain of interrupts that work to limit the size and number of idle periods on the system. For example, frequent reads using a small data buffer in a tight loop will generate many more interrupts than a much larger data buffer and longer blocking read calls. Developers are encouraged to batch their I/O requests to the degree possible in order to avoid interrupting system idle periods needlessly.
Frequent I/O operations represent another pitfall in programming for energy efficiency. Frequent, small reads and writes generate a chain of interrupts that work to limit the size and number of idle periods on the system. For example, frequent reads using a small data buffer in a tight loop will generate many more interrupts than a much larger data buffer and longer blocking read calls. Developers are encouraged to batch their I/O requests to the degree possible in order to avoid interrupting system idle periods needlessly.