Reduce data redundancy

From Green software

(Difference between revisions)
Jump to: navigation, search
(New page: To make sure no data is lost, it is often backed up and stored in different locations. Software architects not always consider the amounts of energy consumed by the transportation and stor...)
Current revision (14:06, 15 September 2010) (edit) (undo)
 
Line 1: Line 1:
To make sure no data is lost, it is often backed up and stored in different locations. Software architects not always consider the amounts of energy consumed by the transportation and storage of all this redundant data. Sometimes redundancy is necessary, but at least energy efficiency could be considered in a trade-off regarding data redundancy.
To make sure no data is lost, it is often backed up and stored in different locations. Software architects not always consider the amounts of energy consumed by the transportation and storage of all this redundant data. Sometimes redundancy is necessary, but at least energy efficiency could be considered in a trade-off regarding data redundancy.
 +
 +
== Sources ==
 +
This best practice was recognized as such by IT professionals, described in [[Energy efficient software (Master Thesis)|''Energy efficient software'']].

Current revision

To make sure no data is lost, it is often backed up and stored in different locations. Software architects not always consider the amounts of energy consumed by the transportation and storage of all this redundant data. Sometimes redundancy is necessary, but at least energy efficiency could be considered in a trade-off regarding data redundancy.

Sources

This best practice was recognized as such by IT professionals, described in Energy efficient software.

Personal tools