The Energy Saved By Ditching DVDs Could Power 200,000 Homes
Daniel_Stuckey (2647775) writes "The environmental benefits of streaming a movie (or downloading it) rather than purchasing a DVD are staggering, according to a new U.S. government study by researchers at the Lawrence Berkeley National Laboratory. If all DVDs purchased in 2011 were streamed instead, the energy savings would have been enough to meet the electricity demands of roughly 200,000 households. It would have cut roughly 2 billion kilograms of carbon emissions. According to the study, published in Environmental Research Letters, even when you take into account cloud storage, data servers, the streaming device, streaming uses much less energy than purchasing a DVD. If, like me, you're thinking, 'who buys DVDs anymore, anyways?', the answer is 'a lot of people.'" The linked paper is all there, too — not just an abstract and a paywall.
If you read the article in detail, the energy cost for a DVD rented or purchased by mail is pretty much identical to that of one streamed (figure 4.)
The purported energy cost difference between DVD and streaming is entirely due to the fact that they assume you drive to the store to buy or rent the DVD. (In fact, there is actually a tiny bit more carbon emitted if you stream instead of rent or buy by mail, if you look at the right image on figure 4).
I assume if you buy or rent from a store you're going to visit anyway, this differnce vanishes
http://www.geoffreylandis.com
So all of the 'environmental benefits' boil down to the assumptions they make about those purchases.
Perhaps it's just me, but I would lean more towards people already being at a store/mall for another purpose and picking up the dvd as an impulse buy. Non-impulse buys of dvd would seem to more logically take place over the internet.
Don't complain about syntax, grammar, or spelling. There is no.hell like input on android.
Don't start all this "can't tell the difference" crap. Until you can get internet lags and stutters completely eliminated we'll be able to tell the difference.
All "clouds" must be over the internet. The whole point of "the cloud" is that it is located remotely, on someone else's hardware, managed by someone else's IT staff. Elsewise, it's nothing more than the same data center you had a decade ago.
Most clouds I've worked with to date have been corporate clouds. No internet involved. Networks, yes; but no internet. Lag was never a problem for me in those environments.
All "clouds" must be over the internet. The whole point of "the cloud" is that it is located remotely, on someone else's hardware, managed by someone else's IT staff. Elsewise, it's nothing more than the same data center you had a decade ago.
Not necessarily true. One aspect of the cloud is being able to rapidly expand capacity or relocate workloads based on application needs. "located remotely, on someone else's hardware, managed by someone else's IT staff" is more like a definition of out-sourcing. Cloud can be on my hardware, managed by my staff, be migrated to or augmented by remote capacity during peak times or special circumstances.
You are both idiots for not knowing how to argue. Zeromous, perhaps your point is "Someone can be hosting a cloud locally to support a business/agency. So it can be available over 1gbit LAN with indiscernible latency, or be in a geographically close data center with an interconnect of equivilant bandwidth."
But you didn't provide any supporting facts so your equally ridiculous.
Zeomous of poor reading comprehension says: "I'm still trying to figure out what you exact beef here is." when Russ had just said "lags and stutters".
Anyhow, usually what people host locally is not a cloud infrastructure, since if you're not doing hosting for third parties, and only your own organization, your virtuallization needs are met by a simpler cluster architecture. Some call it a cloud infrastructure, but usually is just a virtuallized cluster. Virtuallization != cloud. Cloud involves virtualization. Not all virtualization is a cloud. Very much the not-all-black-birds-are-crows kind of thing.
Actual KW saved by not running directly on metal, and squeezing every possible resource out of a highly efficient and redundant server.
On the other hand, many "cloud" services are actually grid services that run on many, redundant, small servers, in contrast to the blade center HP and IBM tries to shove down your throat. One example is GMail and the assorted google services. So, while I understand your point about virtualization, cloud and virtualization are two very different and very distinct things.
It means asset depreciation is much lower, so server churn is much lower (less carbon, less waste less garbage)
It depends how you measure it. In a pure cpu-power-per-watt, 1U servers are way cheaper than an equivalent blade solution, easier to service, and will run cooler. They do take more space, but asset depreciation on a 50K blade cage vs 30K of 1U servers is bigger in the blades.
every watt is consumed rather than dissipated as heat
Well, its not, and this is one of the biggest fallacies of virtualization. It wildly varies according to the workload and your configuration. For small workloads, you may even spend more in hardware to provide proper virtualization than you had to pay for a metal solution. You do gain flexibility, and yes, when well done, you may take more advantage of your hardware, but this is not a novel concept. When possible, solutions like linux containers, solaris zones and freebsd jails allows at least some level of flexibility with a smaller execution footprint.
And regarding usage... well, most cpu's even implement an instruction that internally halts the cpu if not in use. Cpu consumption varies according to the workload, and most of the specs mention max consumption, not average consumption. It may even happen that your beefier setup actually spends more power per vm than single dedicated servers.
It means common parts for all servers which leads to less manufacturing waste.
Yes, but is it cheaper? As an example, almost all industrial processes wastes copious amounts of water, when often more sofisticated and reusable replacements are available. But water is cheaper. Its a bit like saying "this aluminium package is 20% smaller, so we can stop using cardboard packaging because it generates less waste". I would like to see proper metrics on that, not sure if it is that obvious.