Hammers, hurricanes, and HTML
summary
Content states the common bytes‑transferred model is misleading and gives concrete alternatives: 54% user‑device energy comes from displays and device turnover, data centers track better via CPU time for data centers, and networks behave almost constant. Practical work ships an Astro middleware that measures server kilowatt‑hours and client CO2, enforces a 500 KB upload limit, and fixes missing cache headers; demo runs and exposes where spikes come from, with links to Sustainable Web Design, Web Carbon Calculator, AWS and provider emission data.
AI-written summary · about
chapters (11)
- 0:00Green computing introduction
- 1:05Research motivation
- 2:09Carbon Calculator limits
- 7:08Sustainable Web Design
- 13:51Flaws in bytes model
- 18:48Mobile energy usage
- 20:56CPU time measurement
- 23:00CO2 measurement demo
- 28:24Cache headers debugging
- 29:28File size limits
- 32:16Closing resources
related talks
26mSaving the world, one line at a time
55mCode that Won't Heat the Planet: Engineering Sustainable Software for a Better Future
27mWorking towards a greener world from behind the keyboard
49mDesigning Energy Efficient Websites
38mBetter Coding for the Climate?!
52mPanel 2: Network
51mdisplay: green; applying the web sustainability guidelines
44mCloud computing and carbon emissions