permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit da7e147b3add160fae358ae29ac4350acd33b77d
parent 9a5051603b7dd144b8974df5330f1c0f7b17b49e
Author: viznut_web <viznut_web@web>
Date:   Fri, 17 Jun 2022 13:03:22 +0200

empty web commit

Diffstat:
MSolar_Protocol.mdwn | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Solar_Protocol.mdwn b/Solar_Protocol.mdwn @@ -2,7 +2,7 @@ A problem with Solar Protocol is that it either neglects the energy requirements of the [[Internet]] infrastructure that lies between the solar-powered servers and the users, or takes them as a constant that only depends on the amount of transferred data. However, we can be fairly sure that routing a packet across the world takes much more energy than routing it across a country. -If the power consumption of a server is small to begin with, its "greenness" may very well get negated by a bad routing decision. It may very well be "greener" to just route a user to nearby grid-powered data center than to a solar-powered server on the other side of the world. +If the power consumption of a server is small to begin with, its "greenness" may very well get negated by a bad routing decision. It may very well be "greener" to just route a user to a nearby fossil-powered data center than to a solar-powered server on the other side of the world. Taking the network into the equation is difficult because even academic estimations of the power consumption of Internet routing have varied by several orders of magnitude. Still, there seem to be no mentions of this issue on the Solar Protocol website, even though it discusses the energy consumption in the server side and the browser side. Given the prominence of SP in the media, it is highly unlikely that the people involved have not heard about this kind of critique.