Batched IO

From Green software

(Difference between revisions)
Jump to: navigation, search
(Sources)
Line 6: Line 6:
== Sources ==
== Sources ==
This best practice was recognized as such by IT professionals, described in [[Energy efficient software (Master Thesis)|''Energy efficient software'']].
This best practice was recognized as such by IT professionals, described in [[Energy efficient software (Master Thesis)|''Energy efficient software'']].
 +
<br />
 +
This best practice is mentioned in:<br />
 +
Petter Larsson. 2008. Energy-Efficient Software Guidelines. [http://software.intel.com/en-us/articles/energy-efficient-software-guidelines/ White Paper for the Intel Software Solutions Group].

Revision as of 14:43, 16 September 2010

Instead of reading contents from a file or connection whenever needed, this traffic can be batched and stored in a buffer. Batching input and output can reduce energy efficiency because input and output devices can be powered down by the operating system. Especially when reading input and writing output in an iterating loop can be avoided, batching can be quite profitable.

Drawbacks

By reading more data from or storing more data in memory then needed, the memory can be loaded more than needed. When this forces the system to use virtual memory from disk or disallows the memory to power down batched IO can cause a decrease in energy efficiency for a system.

Sources

This best practice was recognized as such by IT professionals, described in Energy efficient software.
This best practice is mentioned in:
Petter Larsson. 2008. Energy-Efficient Software Guidelines. White Paper for the Intel Software Solutions Group.

Personal tools